Customer Review

Customer Readiness Summary

Readiness classification: Ready for customer clarification workshop

Recommendation

Use this package as the evidence baseline for a customer clarification workshop. It is not yet customer-ready for approval because key product boundary, interface, ownership, and TARA/residual-risk questions remain open.

Current Gate

Traceability gate: WARN - Customer Clarification Needed
OCR status: false
Downstream direct PDF analysis: false
Unsupported architecture placeholders unresolved: 0

Known Limitations

Low-confidence requirements remain visible with RFQX-06 review statuses.
Final TARA and residual-risk approval are not claimed.
Exact deployment topology and ownership must be confirmed by the customer and supplier.

Customer Clarification Questions

Generated: 2026-06-23T20:54:39+00:00

Total clarification questions: 472

Product/System Boundary

CQ-BOUNDARY-03

Question: Confirm the customer decision needed to baseline this requirement item: Term 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. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P1
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-1001379436-P10-000-01-0003
Source document: source document page 3
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Not Applicable
Rationale: Requirement was not low-confidence in the extracted baseline.
Classification: Needs Customer Clarification

CQ-BOUNDARY-05

Question: Confirm the customer decision needed to baseline this requirement item: Note: The vehicle manufacturer and supplier shall collaboratively define the context of the system or function to enable the supplier performing the risk assessment.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P1
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-1001379436-P10-000-01-0011
Source document: source document page 5
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Not Applicable
Rationale: Requirement was not low-confidence in the extracted baseline.
Classification: Needs Customer Clarification

CQ-BOUNDARY-127

Question: Confirm the customer decision needed to baseline this requirement item: Table 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).. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P1
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0005
Source document: source document page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Not Applicable
Rationale: Requirement was not low-confidence in the extracted baseline.
Classification: Needs Customer Clarification

CQ-BOUNDARY-158

Question: Confirm the customer decision needed to baseline this requirement item: 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.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P1
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0246
Source document: source document page 52
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Not Applicable
Rationale: Requirement was not low-confidence in the extracted baseline.
Classification: Needs Customer Clarification

CQ-BOUNDARY-199

Question: Confirm the customer decision needed to baseline this requirement item: 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 }. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P1
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS154-0035
Source document: source document page 9
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Not Applicable
Rationale: Requirement was not low-confidence in the extracted baseline.
Classification: Needs Customer Clarification

CQ-BOUNDARY-201

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P1
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0006
Source document: source document page 4
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Not Applicable
Rationale: Requirement was not low-confidence in the extracted baseline.
Classification: Needs Customer Clarification

CQ-BOUNDARY-01

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: This 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-1001379436-P10-000-01-0001
Source document: source document page 3
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-02

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-1001379436-P10-000-01-0002
Source document: source document page 3
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-04

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Cybersecurity principles are high level requirements that drive development and refinement of functional and technical cybersecurity requirements.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-1001379436-P10-000-01-0006
Source document: source document page 5
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-06

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The vehicle manufacturer reserves the right to perform penetration testing on the ECU to identify potential vulnerabilities.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-1001379436-P10-000-01-0020
Source document: source document page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-07

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-1001379436-P10-000-01-0023
Source document: source document page 7
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-08

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The actuator is placed outside of the gearbox. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0003
Source document: source document page 4
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-09

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The clutch force acting on the pushrod is defined in Appendix A. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0046
Source document: source document page 12
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-10

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The pushrod position when clutch is at rest and only preload force is applied, will vary randomly within 2 mm (± 1mm from FCCP).. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0048
Source document: source document page 12
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-100

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: The sequence shown in the following figure shows the post-programming step of phase #1.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0146
Source document: source document page 19
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-101

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0147
Source document: source document page 19
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-102

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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 programming. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0149
Source document: source document page 19
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-103

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The application reads and applies the boot parameter values from the boot parameter module.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0150
Source document: source document page 20
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-104

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0151
Source document: source document page 20
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-105

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0155
Source document: source document page 20
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-106

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0156
Source document: source document page 20
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-107

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: , the client post physically addressed authentication (0x29) request with subfunction deAuthenticate (0x00) based on CVS31 with SPRMIB not set.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0158
Source document: source document page 20
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-108

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: In this step, it is client dependent if and what entities are relevant to be set after updating the software.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0160
Source document: source document page 20
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-109

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: For reference on EMP control routine, see CVS33.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0162
Source document: source document page 20
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-11

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Minimum diagnostic feedback described in req. 6.22.1 - 6.22.11.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0127
Source document: source document page 25
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-110

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: This is to shorten the time for the data transfer from the tester to the ECU to be programmed.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0174
Source document: source document page 21
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-111

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0180
Source document: source document page 21
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-112

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0191
Source document: source document page 22
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-113

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: If an encryptionEntry match is found, see chapter 9.3.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0210
Source document: source document page 25
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-114

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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 Request. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0249
Source document: source document page 31
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-115

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: SUV2_REQ 4 prevents the scenario of erasing the copied bootloader while boot loader update and leaving the ECU without any bootloader.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0253
Source document: source document page 32
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-116

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: This RoutineIdentifier value allows the client to start a routine which erases ECU internal non- volatile memory.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0255
Source document: source document page 32
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-117

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: prevents the scenario of erasing the copied bootloader while boot loader update and leaving the ECU without any bootloader.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0259
Source document: source document page 32
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-118

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 8.3.4 Routine 0xFF00 Parameters 8.3.4.1 Parameter addressAndLengthFormatIdentifier. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0264
Source document: source document page 34
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-119

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The client may opt to execute this routineIdentifier as a standalone procedure to check to perform a software consistency check.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0272
Source document: source document page 35
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-12

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Motor rotation feedback, short circuit / open load. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0130
Source document: source document page 25
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-120

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 8.4.4 Routine 0xFF01 Parameters 8.4.4.1 Parameter routineStatus routineResult. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0283
Source document: source document page 36
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-121

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: This parameter consist of the length of the routineResultProof parameter.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0291
Source document: source document page 37
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-122

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: In DSC sanity check, there is a specific area of application sanity check which depends on the context of the general DSC.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0324
Source document: source document page 41
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-123

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The referenceHash defines the reference hash value to be used in the hash comparison.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0327
Source document: source document page 41
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-124

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The received data to decrypt may only be parts of a software module and it will be based on the range defined.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0344
Source document: source document page 42
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-125

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: EncryptionEntries are not present if software is not encrypted.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0345
Source document: source document page 42
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-126

Question: Confirm the customer decision needed to baseline this requirement item: Foreword This CVS124 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0002
Source document: source document page 2
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-128

Question: Confirm the customer decision needed to baseline this requirement item: May This word, or the adjective “Optional”, means that an item is truly optional.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0010
Source document: source document page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-129

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: SUPPLIER in the Changing column means that the DID can be changed only at the supplier premises for non-programmable ECUs. Data identifier details.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0021
Source document: source document page 9
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-13

Question: Confirm the customer decision needed to baseline this requirement item: Internally stored parameters may be accessible only using supplier defined tools .. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0141
Source document: source document page 27
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-130

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 5.2.1.7 DID 0xF189 vehicleManufacturerECUSoftwareVersionNumberDataIdentifier. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0033
Source document: source document page 12
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-131

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: This identifier is used for follow up and quality check at production and service and for legal reasons if applicable.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0041
Source document: source document page 14
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-132

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The current date as received on CAN or other ECU-external source at first reception of a valid signal after a software update.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0062
Source document: source document page 20
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-133

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: This identifier is used to link a ECU HW to its specialized security attributes.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0066
Source document: source document page 22
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-134

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The value to be stored is fetched from TRATON backend system in production.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0067
Source document: source document page 22
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-135

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The default diagnostic session is referred to as “defaultSession”.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0076
Source document: source document page 23
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-136

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Diagnostics safe state is the following conditions that needs be satisfied to ensure vehicle is not in operation while performing certain diagnostics services.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0085
Source document: source document page 25
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-137

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . 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. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0098
Source document: source document page 28
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-138

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . If the client requests an ECUReset (0x11) with the sub-function HardReset (0x01) in the boot loader ExtendedSession or ProgrammingSession, the reset is performed.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0105
Source document: source document page 29
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-139

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . If the client requests an ECUReset (0x11) with the sub-function HardReset (0x01) in the DefaultSession in the boot loader, the reset is performed.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0109
Source document: source document page 29
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-14

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Umax: - - 32/36/48 A Specific test relations TBD. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0157
Source document: source document page 29
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-140

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . 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).. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0111
Source document: source document page 29
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-141

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . 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).. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0115
Source document: source document page 29
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-142

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: . 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0118
Source document: source document page 30
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-143

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: . 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0119
Source document: source document page 30
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-144

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: . 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0120
Source document: source document page 30
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-145

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: . 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0121
Source document: source document page 30
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-146

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: . 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0122
Source document: source document page 30
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-147

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: . 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0123
Source document: source document page 30
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-148

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: . If the client requests an ECUReset (0x11) with the sub-function HardReset (0x01) in a DefaultSession in the application software, a restart is performed.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0124
Source document: source document page 30
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-149

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: . If the client requests an ECUReset (0x11) with the sub-function HardReset (0x01) in the ExtendedSession in the application software a restart is performed.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0125
Source document: source document page 30
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-15

Question: Confirm the customer decision needed to baseline this requirement item: CVS41 limits may go below this value. Valid only for ECU and communication function. For clutch actuation see req. 5.13. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0158
Source document: source document page 29
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-150

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . If the client requests an ECUReset (0x11) with the sub-function KeyOffOnReset (0x02) in the DefaultSession in the boot loader, the reset is performed.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0126
Source document: source document page 30
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-151

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0127
Source document: source document page 30
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-152

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Its upto the ECU to include the conditions that are relevant for that particular ECU, but needs to be agreed with Vehicle Manufacturer.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0143
Source document: source document page 32
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-153

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0151
Source document: source document page 33
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-154

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: After receiving CommunicationControl service request, ECUs could still keep sending some networks messages/signals to keep a healthy vehicle system.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0173
Source document: source document page 35
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-155

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: A functionally addressed TesterPresent may arrive at any time during another request.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0181
Source document: source document page 37
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-156

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Legislated OBD relevant ECUs have to support legislated OBD standards.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0221
Source document: source document page 42
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-157

Question: Confirm the customer decision needed to baseline this requirement item: 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.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0240
Source document: source document page 49
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-159

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 5.5.17 SecuredDataTransmission (0x84) service. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0299
Source document: source document page 63
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-16

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The life length requirement is minimum 3000 operating hours per year for 15 years. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0197
Source document: source document page 38
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-160

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: This RoutineIdentifier enables the client to query the state of the programming preconditions in the server and applicable only for programmable ECUs.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0326
Source document: source document page 66
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-161

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: SUV2_INFO 114 in CVS123 prevents the scenario of erasing the copied bootloader while boot loader update and leaving the ECU without any bootloader.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0344
Source document: source document page 69
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-162

Question: Confirm the customer decision needed to baseline this requirement item: The RoutineIdentifier may verify the authenticity of the received file package. See CVS123 and. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0361
Source document: source document page 74
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-163

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The total vehicle distance at occurrence is used in DTCExtDataRecords, see section 5.5.10.2.8.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS124-0419
Source document: source document page 82
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-164

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0001
Source document: source document page 1
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-165

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0005
Source document: source document page 4
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-166

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The RBAC logic is typically part of the ECU application- and boot-software.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0007
Source document: source document page 4
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-167

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The RBACC is typically injected into the ECU during production, using a secure protocol.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0008
Source document: source document page 4
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-168

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: As previously mentioned, each ECU (supporting RBAC) will be programmed with an RBACC, RBAC Configuration, containing the rules to drive the RBAC logic.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0009
Source document: source document page 4
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-169

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The RBACC contains one or several role-configurations (see Figure 2 for a visual representation).. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0010
Source document: source document page 4
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-17

Question: Confirm the customer decision needed to baseline this requirement item: Reduced versions of test procedure II may be agreed and used during various tests.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0222
Source document: source document page 41
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-170

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: 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.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0012
Source document: source document page 5
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-171

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: A role-configuration, in its turn, contains one or many rules (see Figure 2 for a visual representation).. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0013
Source document: source document page 5
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-172

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0021
Source document: source document page 5
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-173

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0022
Source document: source document page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-174

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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).. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0025
Source document: source document page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-175

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: See Annex B for a more detailed example of RBACC.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0027
Source document: source document page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-176

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Allow rules defined in role 0 are an exception to this requirement, see 3.13.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0029
Source document: source document page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-177

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The version specifies the structure of RBACC.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0031
Source document: source document page 8
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-178

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: See RBACStructureVersion definition in CVS124.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0038
Source document: source document page 8
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-179

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: This field identifies the RBACC using 16 octets.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0039
Source document: source document page 8
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-18

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS40 §5.5 TC-05 Temperature cycle test Tmax.tes= +120°C, Tmin.test=-40°C Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0223
Source document: source document page 43
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-180

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: See RBACIdentifierNumber definition in CVS124.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0042
Source document: source document page 8
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-181

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: A 32-bit unsigned integer that represents one role.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0043
Source document: source document page 8
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-182

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The diagnostic pattern identifies the diagnostic request.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0046
Source document: source document page 9
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-183

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: This type of rule can be used to create rules for all types of diagnostic requests.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0047
Source document: source document page 9
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-184

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0052
Source document: source document page 9
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-185

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: This type of rule can be used to create rules for all types of diagnostic requests that makes use of RIDs.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0056
Source document: source document page 10
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-186

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: 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).. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0059
Source document: source document page 11
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-187

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: A snippet from https://datatracker.ietf.org/doc/html/rfc5280#section-4.1 that specifies the layout of a certificate extension.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0061
Source document: source document page 11
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-188

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Inside the extnValue (see snipped above) is one instance of a RBACC (see 3.3).. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0063
Source document: source document page 12
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-189

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: As previously stated and as show in Figure 4, deny rules takes precedence over allow rules.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0069
Source document: source document page 15
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-19

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS40 §5.11 TC-11 Corrosion in flowing mixed noxious gas N. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0229
Source document: source document page 43
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-190

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: 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.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0070
Source document: source document page 15
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-191

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The “request.conditions COMPLIES_WITH rule.settings” refers to evaluate if the request conditions fulfils the expected rule settings.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0072
Source document: source document page 16
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-192

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS151-0090
Source document: source document page 20
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-193

Question: Confirm the customer decision needed to baseline this requirement item: 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.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS154-0001
Source document: source document page 1
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-194

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: See further chapter 3.2 DSC ASN.1 definition for element types.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS154-0005
Source document: source document page 4
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-195

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: • version: specifies a version of the DSC structure, namely the DSC ASN.1 definition and its elements within the DSC instance.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS154-0007
Source document: source document page 5
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-196

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The encryptionEntry is of ASN.1 type CHOICE stipulating the decryption strategy for a piece of data.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS154-0028
Source document: source document page 7
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-197

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: See 3.2 for the context-specific tag number for the EncryptionEntry choices.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS154-0030
Source document: source document page 7
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-198

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: An ItemEntry is of ASN.1 type CHOICE, where the choice stipulates the type of item the ItemEntry holds.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS154-0033
Source document: source document page 9
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-20

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS40 §6.4 TM-03 Random vibration and thermal cycle P1 Test 2 Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0234
Source document: source document page 43
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-200

Question: Confirm the customer decision needed to baseline this requirement item: Foreword This CVS31 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0002
Source document: source document page 3
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-202

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: In this document, each subFunction (ISO 14229-1:2020) is described in its own sub-section.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0013
Source document: source document page 7
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-203

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: For details in how to validate a client certificate, refer to chapter 4.1.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0023
Source document: source document page 9
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-204

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: 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). Additionally, the field proves that the same message sent by the client has been received by the server and vice-versa.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0032
Source document: source document page 11
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-205

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: This field provides the client with the necessary server-side data for the chosen key-exchange scheme/algorithm.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0035
Source document: source document page 11
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-206

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: 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).. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0039
Source document: source document page 11
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-207

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: 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).. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0050
Source document: source document page 13
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-208

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The reason for the concatenation, is to ensure that the full communication (all sent and received requests and responses) has integrity.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0052
Source document: source document page 13
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-209

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: This field provides the server with the necessary client-side data for the chosen key-exchange scheme/algorithm.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0053
Source document: source document page 13
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-21

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS40 §6.5 TM-04 Gravel bombardment and impact Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0235
Source document: source document page 43
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-210

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: This chapter specifies the behaviour of the deAuthenticate subfunction.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0064
Source document: source document page 15
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-211

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: A certificate without NodeUID extension implies that the certificate is applicable for any NodeUID.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0085
Source document: source document page 18
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-212

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: The maximum number of elements in the list (number of ids) is limited by the maximum size of the certificate.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0086
Source document: source document page 18
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-213

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0092
Source document: source document page 18
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-214

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: The notBefore and notAfter are received as fields in the certificate while Certificate-Time is the EMP entity defined in CVS34.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0107
Source document: source document page 19
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-215

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0112
Source document: source document page 20
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-216

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: • Successful deAuthenticate (see 3.3) subFunction (ISO 14229-1:2020).. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0115
Source document: source document page 20
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-217

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: • Client D-RBACC, if provided in the client’s certificate. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0123
Source document: source document page 21
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-218

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: The server ephemeral private key is the pair of the public key (ephemeralPublicKeyServer) sent as verifyCertificateBidirectional response.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0126
Source document: source document page 21
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-219

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: • Client roles (ECU diagnostic Role extension in client’s certificate). This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0131
Source document: source document page 21
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-22

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS40 §7.1 TL-01 Life length As per Chapter 8 Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0238
Source document: source document page 43
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-220

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: • Client D-RBACC, if provided in the client’s certificate. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0132
Source document: source document page 21
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-221

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: 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.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0135
Source document: source document page 22
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-222

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: An overview of the key-exchange process is shown in Figure 4.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0136
Source document: source document page 22
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-223

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0139
Source document: source document page 22
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-224

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The SessionKey is referred as SecuredDataTransmissionKey in (CVS32).. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0140
Source document: source document page 22
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-225

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Updated document quirks chapter Removed the information that italic terms are often clickable.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0229
Source document: source document page 30
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-226

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Reformulation for clarity improvement Changed. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0230
Source document: source document page 30
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-227

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: (Maximum size of elements is to be defined by max size of certificate) Added. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0244
Source document: source document page 30
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-228

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: (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. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0245
Source document: source document page 30
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-229

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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 subfunction. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS31-0254
Source document: source document page 30
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-23

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS40 §7.2.2 TL-03 Extended thermal shock air TBD. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0240
Source document: source document page 43
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-230

Question: Confirm the customer decision needed to baseline this requirement item: Foreword This CVS32 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS32-0002
Source document: source document page 2
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-231

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The 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]. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS32-0005
Source document: source document page 4
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-232

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS32-0006
Source document: source document page 4
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-233

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: ECUs with diagnostic servers in multiple execution states, e.g.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS32-0013
Source document: source document page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-234

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: A prerequisite for the SDT service is that a SecuredDataTransmissionKey has been established between client and server using the 0x29 service [6].. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS32-0015
Source document: source document page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-235

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: The 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.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS32-0045
Source document: source document page 10
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-236

Question: Confirm the customer decision needed to baseline this requirement item: The client may alter the CipherScheme between SDT requests within the same SDT sequence.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS32-0049
Source document: source document page 10
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-237

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: Since the two CipherSchemes require different key material, the KDF has to be re-run if the CipherScheme changes.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS32-0050
Source document: source document page 10
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-238

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: In the following, these state variables are called PSIGENCRYPT (Previous SIGENCRYPT) and PKEY (Previous KEY).. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS32-0052
Source document: source document page 10
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-239

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: okm is the output key material octet string of length L.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS32-0062
Source document: source document page 12
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-24

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS40 §7.2.3 TL-04 High temperature endurance test TBD. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0241
Source document: source document page 43
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-240

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: 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.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS32-0086
Source document: source document page 14
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-241

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: 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.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS32-0112
Source document: source document page 17
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-242

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: This 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS32-0114
Source document: source document page 18
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-243

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Figure 10Figure 10 illustrates error- and state handling in the server’s security sub-layer.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS32-0117
Source document: source document page 18
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-244

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Figure 12Figure 12 illustrates error- and state handling in the client’s security sub-layer.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS32-0138
Source document: source document page 21
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-25

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS40 §7.2.4 TL-05 Endurance test / actuation TBD. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0242
Source document: source document page 43
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-26

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS40 §8.2 TS-02 UV resistance Datasheet sufficient Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0246
Source document: source document page 44
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-27

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS40 §8.3 TS-03 Chemical resistance Application method TBD Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0247
Source document: source document page 44
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-28

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS40 §8.4 TE-01 Isolation resistance and Dielectric strength tests N Exceptions and additional information to CVS41 [Y/N]. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0248
Source document: source document page 44
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-29

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS41 §4.1 TE-00 Operating Voltage Class A for ECU and communication. Class B for clutch actuation Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0250
Source document: source document page 44
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-30

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS41 §4.2 TE-01 Operating Voltage (Long-term overvoltage) Umax: 15 min, functional status Class B Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0251
Source document: source document page 44
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-31

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS46 §4.6.6 Test LFM: Low Frequency Magnetic Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0257
Source document: source document page 47
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-32

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS46 §4.15 Test ESD: Immunity to electrostatic discharge (ESD) Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0266
Source document: source document page 47
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-33

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS46 §4.15.1 Test ESDD: Direct Discharge, Powered up Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0267
Source document: source document page 47
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-34

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS46 §4.15.2 Test ESDI: Indirect Discharge (Powered up) Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0268
Source document: source document page 47
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-35

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS46 §4.15.3 Test ESDH: ESD Handling, Component not energised Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0269
Source document: source document page 47
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-36

Question: Confirm the customer decision needed to baseline this requirement item: CVS46 §5.1 Vehicle test ESD Traton performs Vehicle test, Traton may need support from supplier with any issues originating from the component. Y. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0270
Source document: source document page 47
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-37

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS46 §5.2 Vehicle test RE: Emitted interference of the complete vehicle Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0271
Source document: source document page 47
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-38

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS46 §5.2.1 Vehicle test RE: Protection of receivers outside the vehicle Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0272
Source document: source document page 47
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-39

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS46 §5.2.2 Vehicle test RE: Self interference Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0273
Source document: source document page 47
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-40

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS46 §5.3 Vehicle test charging: Vehicle in the AC charging mode N. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0274
Source document: source document page 47
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-41

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS46 §5.3.1 Vehicle test: AC charging Vehicle in AC charging mode N. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0275
Source document: source document page 47
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-42

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS46 §5.3.2 Vehicle test: DC charging: Vehicle in DC charging mode N. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0276
Source document: source document page 47
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-43

Question: Confirm the customer decision needed to baseline this requirement item: CVS46 §5.4 Vehicle test RI: Immunity of vehicles to radiated fields Traton performs Vehicle test, Traton may need support from supplier with Y. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0277
Source document: source document page 47
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-44

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CVS46 §5.4.1 Vehicle test RI: External interference sources Y. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0278
Source document: source document page 47
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-45

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Field test Traton will perform field tests with the unit mounted in trucks. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0284
Source document: source document page 50
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-46

Question: Confirm the customer decision needed to baseline this requirement item: Unless otherwise stated, valid version is the latest available as of 1st May 2026.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0301
Source document: source document page 52
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-47

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: This needs to be checked with the first test run and if necessary the test cycle used in profile B needs to be changed.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-3299216-1-0309
Source document: source document page 61
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-48

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0001
Source document: source document page 1
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-49

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The vehicle manufacturer implementation of the Authentication service (0x29) is defined in CVS31 and SecuredDataTransmission service (0x84) is defined in CVS32.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0005
Source document: source document page 4
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-50

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0006
Source document: source document page 4
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-51

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0007
Source document: source document page 4
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-52

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0009
Source document: source document page 4
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-53

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: This specification targets ECUs, not clients.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0012
Source document: source document page 4
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-54

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The target readers of this specification are ECU suppliers, which can be either internal or external in relation to the vehicle manufacturer.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0015
Source document: source document page 5
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-55

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0016
Source document: source document page 5
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-56

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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 Definition. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0017
Source document: source document page 5
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-57

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0025
Source document: source document page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-58

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0027
Source document: source document page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-59

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: Similarly, informative text is prefixed “SUV2_INFO”.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0033
Source document: source document page 8
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-60

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0045
Source document: source document page 9
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-61

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: The “boot parameter module” permits a generic bootloader to be an ECU application platform (ECU HW + boot loader software).. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0054
Source document: source document page 10
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-62

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: A joint use of program code for communication functions (com stack) by the application and the boot loader is not permitted.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0060
Source document: source document page 11
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-63

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0063
Source document: source document page 11
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-64

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: If a valid application is present in the ECU, some of the services described in the programming sequence will be executed in the application.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0073
Source document: source document page 12
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-65

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0074
Source document: source document page 12
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-66

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: For further information on the service details and programming messages structure regarding the SecuredDataTransmission (0x84) service, refer to CVS32.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0080
Source document: source document page 12
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-67

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: The sequence shown in the following figure shows the Pre-Programming step of phase #1.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0081
Source document: source document page 13
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-68

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: When this step is entered, the ECU is assumed to be in a state which enables it to receive UDS service requests.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0082
Source document: source document page 14
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-69

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The client posts a functionally addressed DiagnosticSessionControl (0x10) service request with sessionType equal to DefaultSession and the SPRMIB not set.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0084
Source document: source document page 14
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-70

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: All servers available on the network and their diagnostic addresses are identified from the positive responses to this request.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0086
Source document: source document page 14
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-71

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The client then posts physically or functionally addressed ReadDataByIdentifier (0x22) service requests to collect additional identification data from each identified server.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0087
Source document: source document page 14
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-72

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0089
Source document: source document page 14
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-73

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: 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.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0090
Source document: source document page 14
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-74

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: For reference on EMP control routine, see CVS33.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0091
Source document: source document page 14
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-75

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: For reference on EMP control routine, see CVS33.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0096
Source document: source document page 14
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-76

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The client posts a functionally addressed DiagnosticSessionControl (0x10) service request with sessionType equal to extended diagnostic session and the SPRMIB set.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0098
Source document: source document page 15
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-77

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0099
Source document: source document page 15
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-78

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0100
Source document: source document page 15
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-79

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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).. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0101
Source document: source document page 15
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-80

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0102
Source document: source document page 15
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-81

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0103
Source document: source document page 15
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-82

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0104
Source document: source document page 15
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-83

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0106
Source document: source document page 15
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-84

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0107
Source document: source document page 15
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-85

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0108
Source document: source document page 15
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-86

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The information to verify integrity of the software is contained in software data security container (SDSC), which is transmitted in P1PreB step.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0111
Source document: source document page 16
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-87

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: If SDSC dictates decryption, the decryption keys are contained in software data security container (SDSC) which is transmitted in P1PreB step.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0113
Source document: source document page 16
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-88

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: The client posts a physically addressed DiagnosticSessionControl (0x10) service request with sub-function parameter diagnosticSessionType set to ProgrammingSession and the SPRMIB not set.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0115
Source document: source document page 17
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-89

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: If CommunicationControl has not been previously called in the Extended Diagnostic Session the server rejects the request with negative response code NRC 0x22 (conditionsNotCorrect).. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0116
Source document: source document page 17
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-90

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: Implementation hint: If the server is executing the application the server sets a “programming request” flag (C2, see section Boot software session requirements).. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0117
Source document: source document page 17
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-91

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0118
Source document: source document page 17
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-92

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: Finally, the boot loader sends a positive response.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0122
Source document: source document page 17
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-93

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0129
Source document: source document page 18
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-94

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0130
Source document: source document page 18
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-95

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0131
Source document: source document page 18
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-96

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0132
Source document: source document page 18
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-97

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0133
Source document: source document page 18
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-98

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The response of this routineIdentifier allows the client to identify if the specific transferred block is corrupted.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0139
Source document: source document page 18
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-99

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: , 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related Related requirements: RFQX-CVS123-2-0143
Source document: source document page 18
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

Network and External Interfaces

CQ-INTERFACE-01

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The actuator will be controlled by a position and speed demand by CAN-bus. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-3299216-1-0005
Source document: source document page 4
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-02

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The actuator will be controlled by a position and speed demand by a 1kHz PWM signal on wake up connection. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-3299216-1-0006
Source document: source document page 4
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-03

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-3299216-1-0023
Source document: source document page 9
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-04

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: ) 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-3299216-1-0053
Source document: source document page 13
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-05

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Req. 6.3.1 to 6.3.5 describe the various control modes that can be requested via CAN (Ref 14.14). This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-3299216-1-0080
Source document: source document page 20
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-06

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: CAN FD: 4000 - - kbit/s Figure 15 - Reference circuit. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-3299216-1-0173
Source document: source document page 34
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-07

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS123-2-0008
Source document: source document page 4
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-08

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: If servers which support wake-up on CAN are not awake before, this request causes them to wake-up.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS123-2-0085
Source document: source document page 14
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-09

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Details over the integrity check can be found on chapter 9.2.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS123-2-0280
Source document: source document page 35
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-10

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The receipt number is received as part of the EMP message whenever a SDSC is set, please refer to CVS34.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS123-2-0293
Source document: source document page 37
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-11

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: The Non-volatile server memory programming complete flow can be found in Annex B.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS123-2-0346
Source document: source document page 42
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-12

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS124-0102
Source document: source document page 28
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-13

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Link Control (0x87) service is only applicable to CAN & CAN FD.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS124-0194
Source document: source document page 38
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-14

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 5.5.17.1.1 Request message data-parameter definition. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS124-0301
Source document: source document page 63
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-15

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 5.6.2.5 Message flow example(s) RoutineControl (EraseMemory) Example #1: Request: client → server. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS124-0357
Source document: source document page 72
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-16

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Each rule can be of either DENY or ALLOW type.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS151-0015
Source document: source document page 5
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-17

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS151-0064
Source document: source document page 12
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-18

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS31-0069
Source document: source document page 15
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-19

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS31-0072
Source document: source document page 16
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-20

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0010
Source document: source document page 6
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-21

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Figure 1 shows the layout of an SDT message with its protocol elements (for details refer to ISO 14229-1:2020 [1]).. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0011
Source document: source document page 6
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-22

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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].. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0018
Source document: source document page 7
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-23

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: This specification defines two counters, one for the request messages and one for responses.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0022
Source document: source document page 7
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-24

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The reason for the two separate counters is that the UDS standard allows for a request to result in multiple responses, e.g.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0023
Source document: source document page 7
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-25

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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).. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0024
Source document: source document page 7
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-26

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0032
Source document: source document page 8
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-27

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The server handles the exhaustion of PREQARC and PRESARC with its “normal behavior”.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0034
Source document: source document page 8
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-28

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The requirements above are illustrated in Figure 2.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0037
Source document: source document page 8
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-29

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0038
Source document: source document page 8
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-30

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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. This TAG is used to guarantee request/response coherency and the corresponding state variable is called PREQTAG (Previous REQuest TAG).. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0039
Source document: source document page 9
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-31

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The requirements regarding PREQTAG are detailed in sections 3.2.2 and 3.2.3 since they differ slightly between CipherSchemes.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0041
Source document: source document page 9
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-32

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Figure 3 illustrates transaction coherency and the use of PREQTAG.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0042
Source document: source document page 9
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-33

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The authenticity, and optionally confidentiality, of an SDT message is provided by the CipherScheme with which the SDT message is authenticated/encrypted.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0043
Source document: source document page 9
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-34

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Figure 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. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0055
Source document: source document page 11
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-35

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: Example: “SDT_0x84_KEY” = 5344545F307838345F4B4559 (UTF-8 encoded hex) CipherScheme = 02 (SDT_AEAD_CHACHA20_POLY1305) ➔ info := 5344545F307838345F4B455902. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0060
Source document: source document page 11
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-36

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0061
Source document: source document page 11
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-37

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: This section describes a CipherScheme based on AEAD_CHACHA20_POLY1305 [9].. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0063
Source document: source document page 12
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-38

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The above requirements are visualized in Figure 5.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0067
Source document: source document page 12
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-39

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The plaintext (𝑃) and ciphertext (𝐶) octet strings are of the same length and a concatenation of the INTMSGREQID and SRVSPECPARAM protocol elements.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0072
Source document: source document page 12
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-40

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The encircled “||” denotes concatenation and the concatenation order is top to bottom in the figure.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0087
Source document: source document page 14
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-41

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Encrypted data in the figure is denoted “x..x”, one “x” denotes one encrypted octet.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0089
Source document: source document page 14
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-42

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: This 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0090
Source document: source document page 15
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-43

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The above requirements are visualized in Figure 7.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0094
Source document: source document page 15
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-44

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 𝑃: The 𝑃 (Plaintext) is a zero length octet string (null).. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0097
Source document: source document page 15
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-45

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 𝐶: The 𝐶 (Ciphertext) is a zero length octet string (null).. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0098
Source document: source document page 15
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-46

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The encircled “||” denotes concatenation and the concatenation order is top to bottom relative the symbol.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0113
Source document: source document page 17
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-47

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: A UDS request/response, in the figure, means any request/response other than SDT (service 0x84).. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0115
Source document: source document page 18
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-48

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The SDT positive response may of course contain an encapsulated negative UDS response.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0116
Source document: source document page 18
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-49

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Note that the markings in the figure, (“S1” through “S3”), and the values for the state variables are correlated with Figure 3.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0118
Source document: source document page 18
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-50

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: For example, APAR dictates encryption, but SIGENCRYPT does not offer encryption.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0127
Source document: source document page 20
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-51

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: For example, the CipherScheme indicated by SIGENCRYPT produces a TAG of a length different from that indicated by SIGLEN.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0129
Source document: source document page 20
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-52

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: This means that if the server generates an SDT negative response, the server’s state remains unchanged, i.e.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0132
Source document: source document page 20
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-53

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: This means that if the server fails to generate an SDT response, the server’s state remains unchanged, i.e.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0134
Source document: source document page 20
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-54

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: As mentioned above in this specification, the UDS standard allows for a request to result in multiple responses, e.g.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0135
Source document: source document page 20
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-55

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0136
Source document: source document page 21
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-56

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0137
Source document: source document page 21
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-57

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: This means that if the client fails to verify/decrypt the SDT response, the client’s state remains unchanged, i.e.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0148
Source document: source document page 23
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-58

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Messages can get lost going from client to server, or vice versa.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0149
Source document: source document page 23
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-59

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Note that busyRepeatRequest, NRC 0x21 (BRR), can be sent in an SDT negative response, or, encapsulated in an SDT positive response.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0150
Source document: source document page 23
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-60

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: A negative UDS response BRR encapsulated in a positive SDT response can of course never result in the resending of an old SDT request.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0153
Source document: source document page 23
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-61

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: SDT_AES_SIV_CMAC_256 and SDT_CMAC_128 was deprecated and replaced with SDT_AEAD_CHACHA20_POLY1305 and SDT_POLY1305.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0165
Source document: source document page 28
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-62

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: (new cipher-schemes) Updated Figure 4 (new cipher-schemes) Updated. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0169
Source document: source document page 28
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-63

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: (new cipher-schemes) Updated 3.2.2 heading (new cipher-schemes) Updated. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0170
Source document: source document page 28
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-64

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: (new cipher-schemes) Updated Figure 5 annotation (new cipher-schemes) Updated. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0171
Source document: source document page 28
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-65

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: (new cipher-schemes) Updated Figure 6 (new cipher-schemes). This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0181
Source document: source document page 28
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-66

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: (new cipher-schemes) Added Figure 7 (new cipher-schemes) Updated. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0187
Source document: source document page 29
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-67

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: (new cipher-schemes) Updated Figure 8 (new cipher-schemes) Updated. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0200
Source document: source document page 29
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-68

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: (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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0202
Source document: source document page 29
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-INTERFACE-69

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: and updated Figure 9.) 2025-08 1 This standard has been revised and is valid for continued use.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related Related requirements: RFQX-CVS32-0203
Source document: source document page 29
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

Diagnostic and Service Access

CQ-DIAG-01

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: Clients may prefer to implement programming support using other service parameter values or even another set of programming steps than. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS123-2-0013
Source document: source document page 4
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-DIAG-02

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: C2 Also referred to as “programming request” flag.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS123-2-0026
Source document: source document page 6
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-03

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The client post physically addressed RoutineControl (0x31) (EMP) service request with SPRMIB not set and operation-type set to Get (0x01).. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS123-2-0088
Source document: source document page 14
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-04

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The client post physically addressed RoutineControl (0x31) (EMP) service request with SPRMIB not set and operation-type set to Set (0x00).. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS123-2-0092
Source document: source document page 14
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-05

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The client post physically addressed authentication sequence based on CVS31 with SPRMIB not set.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS123-2-0097
Source document: source document page 14
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-06

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS123-2-0105
Source document: source document page 15
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-07

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The client post physically addressed authentication sequence based on Authenticate 0x29 with SPRMIB not set.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS123-2-0123
Source document: source document page 17
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-08

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS123-2-0124
Source document: source document page 17
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-09

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: ) 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS123-2-0126
Source document: source document page 17
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-10

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The client posts physically addressed RequestDownload (0x34) service requests with the SPRMIB not set.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS123-2-0128
Source document: source document page 17
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-11

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The client posts a physically addressed RoutineControl (0x31) (checkMemory) service request with the SPRMIB not set.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS123-2-0136
Source document: source document page 18
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-12

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The client post physically addressed RoutineControl (0x31) (EMP) service request with SPRMIB not set and operation-type set to Set (0x00).. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS123-2-0159
Source document: source document page 20
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-13

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 7.3.4 Service 0x37 Parameters 7.3.4.1 Parameter transferRequestParameterRecord. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS123-2-0231
Source document: source document page 28
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-14

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: • Service 0x37 RequestTransferExit 8.4.4.2 Parameter routineResultProofLength. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS123-2-0290
Source document: source document page 37
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-15

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The format in the DID description in the following tables is given in ODX base data types.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0022
Source document: source document page 9
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-16

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.2.1.3 DID 0xF182 applicationDataIdentificationDataIdentifier. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0026
Source document: source document page 11
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-17

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.2.1.8 DID 0xF18A systemSupplierIdentifierDataIdentifier. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0035
Source document: source document page 13
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-18

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: DID 0xF197 systemNameOrEngineTypeDataIdentifier. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0047
Source document: source document page 16
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-19

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: DID 0xF198 SoftwareItemSemanticDataIdentifiers. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0052
Source document: source document page 17
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-20

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: . Default transition for the start of the software in the server after power-up/wake-up.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0090
Source document: source document page 27
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-21

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Description of the individual transitions as per Figure 2 -State Diagram is explained from. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0091
Source document: source document page 27
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-22

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0095
Source document: source document page 28
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-23

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . If a programming request is active (progRequest P2 == true), the server activates the programming session in the bootloader module.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0096
Source document: source document page 28
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-24

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0097
Source document: source document page 28
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-25

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: . If the client requests a change to the ExtendedSession in the DefaultSession in the application software, the session is changed.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0099
Source document: source document page 28
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-26

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: . 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0100
Source document: source document page 28
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-27

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: . If the client requests a change to the DefaultSession in the ExtendedSession in the application software, the session is changed.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0101
Source document: source document page 28
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-28

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: . If the client requests a change to the ExtendedSession in ExtendedSession in the application software, the server accepts the request.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0103
Source document: source document page 28
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-29

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . If the client requests a change to the DefaultSession in the boot loader ExtendedSession or ProgrammingSession, the reset is performed.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0106
Source document: source document page 29
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-30

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0107
Source document: source document page 29
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-31

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . If the client requests a change to the DefaultSession in the DefaultSession in the boot loader, the server accepts the request.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0108
Source document: source document page 29
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-32

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . If the client requests the ExtendedSession in the DefaultSession in the boot loader, the session is changed.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0110
Source document: source document page 29
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-33

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . If the client requests the ExtendedSession in the ExtendedSession in the boot loader, the server accepts the request.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0112
Source document: source document page 29
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-34

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0113
Source document: source document page 29
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-35

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0114
Source document: source document page 29
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-36

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: . If the client requests the DefaultSession in the DefaultSession in the application, the server accepts the request.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0116
Source document: source document page 29
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-37

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.1.1.1 Request parameter diagnosticSessionType. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0136
Source document: source document page 32
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-38

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: This requirement mitigates DOS (Denial Of Service) attacks. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0170
Source document: source document page 35
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-39

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Refer to ISO 14229-1 for request parameter DTCSettingType.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0188
Source document: source document page 37
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-40

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Request parameter DTCSettingControlOptionRecord. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0189
Source document: source document page 38
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-41

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Refer to ISO 14229-1 for positive response format and parameter.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0190
Source document: source document page 38
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-42

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Refer to ISO 14229-1 for negative response format and codes.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0191
Source document: source document page 38
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-43

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.7 ReadDataByIdentifier (0x22) service 5.5.7.1 Request. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0200
Source document: source document page 39
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-44

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The range of a requested dataRecord value has to be checked by the server if the DID is safety relevant.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0208
Source document: source document page 40
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-45

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Additional client requests which start copying RAM buffer data into non-volatile memory are not allowed.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0211
Source document: source document page 40
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-46

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.9 ClearDiagnosticInformation (0x14) service 5.5.9.1 Request. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0214
Source document: source document page 41
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-47

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.10 ReadDTCInformation (0x19) service 5.5.10.1 Request. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0218
Source document: source document page 41
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-48

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.10.2.1 Response parameter DTCStatusAvailabilityMask. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0231
Source document: source document page 43
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-49

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.12 RoutineControl (0x31) service 5.5.12.1 Request. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0261
Source document: source document page 55
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-50

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.12.1.1 Request parameter RoutineControlType. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0262
Source document: source document page 55
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-51

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0271
Source document: source document page 57
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-52

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.14.2.1 Response parameter lengthFormatIdentifier. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0286
Source document: source document page 61
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-53

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.16 RequestTransferExit (0x37) service 5.5.16.1 Request. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0293
Source document: source document page 62
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-54

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0342
Source document: source document page 69
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-55

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: This is an example where the client requests to erase a module in the server memory by a given memoryStartAddress and memorySize.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0358
Source document: source document page 72
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-56

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: This example reports a failure when the erase operation is started, e.g. memory failure.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0359
Source document: source document page 73
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-57

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: This is an example where the client requests to erase a module with module index 3 in the server’s memory.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0360
Source document: source document page 73
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-58

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: The authenticity verification performed by the RoutineIdentifier 0x2401 Software Installation does not exempt the authenticity verification for RoutineIdentifier 0xFF01 – CheckProgrammingDependencies.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0363
Source document: source document page 74
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-59

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: This is an example where the client requests CheckProgrammingDependencies to finalize the validation after software download.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0394
Source document: source document page 79
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-60

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The checksum was contained in the data stream programmed to the memory.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0395
Source document: source document page 79
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-61

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The occurrence counter is used in DTCExtDataRecords, see section 5.5.10.2.8.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0401
Source document: source document page 80
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-62

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The timestamp of occurrence is used at DTCExtDataRecords, see section 5.5.10.2.8.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0411
Source document: source document page 81
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-63

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The timestamp is presented in SAE J1939-71 format without local hour/minute offsets.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0413
Source document: source document page 81
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-64

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The latest distance value is updated at a change of DTC status bits 0 (testFailed) and 3. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0422
Source document: source document page 82
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-65

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0423
Source document: source document page 82
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-66

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The first distance value is updated at the first change of DTC status bits 0 (testFailed) and 3. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0424
Source document: source document page 82
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-67

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The operational hours at occurrence is used at DTCExtDataRecords, see section 5.5.10.2.8.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0425
Source document: source document page 83
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-68

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The operational hours are presented by a four byte integer, big endian, with , half second per bit (0,5s/bit).. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0426
Source document: source document page 83
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-69

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The latest operational hours value is updated at a change of DTC status bits 0 (testFailed) and 3 (confirmedDTC) both from 0 to 1.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0428
Source document: source document page 83
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-70

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0429
Source document: source document page 83
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-71

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0430
Source document: source document page 83
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-72

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Requirements, Request and response formats for the ControlDTCSetting(0x85) added.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0451
Source document: source document page 90
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-73

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Added semantic Identifier DIDs, changed the NodeUID DID to INTERNAL. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0452
Source document: source document page 90
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-74

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Change in the retrieval method for NodeUID(0xF1AF). This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0454
Source document: source document page 90
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-75

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 0xF1B9 RBACCIdentifierNumber is changed to Mandatory. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0455
Source document: source document page 90
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-76

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 0xF1BA RBACCStructureVersion,bit-length changed. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0456
Source document: source document page 90
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-77

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Modifcations on the bit values and new bit added. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0460
Source document: source document page 90
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-78

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 0x05 is changed to Mandatory 6 Normative references: Updated the referenced documents and versions Removed Requirements and infos. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0461
Source document: source document page 90
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-79

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 0xF19E ODXFileDataIdentifier is removed 2024-10 First issue. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS124-0465
Source document: source document page 90
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-80

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Figure 3 shows the interaction between the diagnostics server and the RBAC enforcer logic.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS151-0067
Source document: source document page 12
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-81

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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).. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS151-0077
Source document: source document page 19
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-82

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: For details on Authentication delay timer, refer to chapter 4.8.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS31-0018
Source document: source document page 8
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-83

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: For details on Authentication completion timer, refer to chapter 4.9.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS31-0044
Source document: source document page 12
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-84

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The signature algorithm in the client, server and authentication CA certificates are ED25519 (1.3.101.112).. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS31-0076
Source document: source document page 16
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-85

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: • A new successful authentication is established.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS31-0116
Source document: source document page 20
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-86

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Authentication state invalidated by the server implies that any unlocked services and sessionKey is locked/invalidated.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS31-0118
Source document: source document page 20
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-87

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: • A3 Timer for passive de-authentication information.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS31-0129
Source document: source document page 21
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-88

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: • Client address that issued the authentication request.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS31-0130
Source document: source document page 21
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-89

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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).. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS31-0144
Source document: source document page 23
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-90

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Two passive de-authentication mechanisms are described in (ISO 14229-1:2020).. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS31-0145
Source document: source document page 23
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-91

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The Authentication completion timer represents the timeframe that the client is allowed to perform proofOfOwnership request after a verifyCertificateBidirectional request.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS31-0159
Source document: source document page 24
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-92

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The Authentication completion timer is started upon positive response for verifyCertificateBidirectional request.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS31-0161
Source document: source document page 24
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-93

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Clarified the signature algorithm to be used over the authentication process Removed. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS31-0249
Source document: source document page 30
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-94

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: (There may be more than one authentication state).. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related Related requirements: RFQX-CVS32-0017
Source document: source document page 6
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

Software Update / IVD

CQ-UPDATE-01

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: This document specifies the method to perform software download using Software Update Variant 2 (SUV2).. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related Related requirements: RFQX-CVS123-2-0004
Source document: source document page 4
Related architecture/security element: Secure update / IVD architecture
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-UPDATE-02

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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).. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related Related requirements: RFQX-CVS123-2-0076
Source document: source document page 12
Related architecture/security element: Secure update / IVD architecture
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-UPDATE-03

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: Programming phase #1 is defined to program a server (e.g., download of application software, application data or boot software).. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related Related requirements: RFQX-CVS123-2-0077
Source document: source document page 12
Related architecture/security element: Secure update / IVD architecture
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-UPDATE-04

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: For each server in the network, depending on whether an application has been successfully flashed before, it will run in application or boot mode.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related Related requirements: RFQX-CVS123-2-0083
Source document: source document page 14
Related architecture/security element: Secure update / IVD architecture
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-UPDATE-05

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: Alternatively, it may be a client strategy to always update certain entities prior to a software update.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related Related requirements: RFQX-CVS123-2-0095
Source document: source document page 14
Related architecture/security element: Secure update / IVD architecture
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-UPDATE-06

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: The sequence in Figure 3 shows the programming step of phase #1.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related Related requirements: RFQX-CVS123-2-0109
Source document: source document page 16
Related architecture/security element: Secure update / IVD architecture
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-UPDATE-07

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: The boot manager notes the programming request and starts the boot loader.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related Related requirements: RFQX-CVS123-2-0119
Source document: source document page 17
Related architecture/security element: Secure update / IVD architecture
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-UPDATE-08

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: Implementation hint: The boot manager recognizes the programming request by checking the “programming request” flag (C2).. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related Related requirements: RFQX-CVS123-2-0120
Source document: source document page 17
Related architecture/security element: Secure update / IVD architecture
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-UPDATE-09

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: Implementation hint: The boot manager or the boot loader resets the “programming request” flag (C2).. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related Related requirements: RFQX-CVS123-2-0121
Source document: source document page 17
Related architecture/security element: Secure update / IVD architecture
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-UPDATE-10

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: It is client specific if P1Pro10 will be sent as part of programming phase #1.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related Related requirements: RFQX-CVS123-2-0134
Source document: source document page 18
Related architecture/security element: Secure update / IVD architecture
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-UPDATE-11

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related Related requirements: RFQX-CVS123-2-0135
Source document: source document page 18
Related architecture/security element: Secure update / IVD architecture
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-UPDATE-12

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: The programming phase #2 (server configuration or also known as parametrization) as defined in ISO 14229-2 is defined in CVS36.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related Related requirements: RFQX-CVS123-2-0163
Source document: source document page 20
Related architecture/security element: Secure update / IVD architecture
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-UPDATE-13

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: This is to keep the programming time to a minimum.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related Related requirements: RFQX-CVS123-2-0170
Source document: source document page 21
Related architecture/security element: Secure update / IVD architecture
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-UPDATE-14

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: This RoutineIdentifier value allows the client to start a consistency check of the server.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related Related requirements: RFQX-CVS123-2-0270
Source document: source document page 35
Related architecture/security element: Secure update / IVD architecture
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

PKI, Keys, Certificates

CQ-PKI-01

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: For information on receipt-keys, please refer to CVS34.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related Related requirements: RFQX-CVS123-2-0296
Source document: source document page 37
Related architecture/security element: Key and Certificate Management
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-PKI-02

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: 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.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related Related requirements: RFQX-CVS31-0034
Source document: source document page 11
Related architecture/security element: Key and Certificate Management
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-PKI-03

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The sessionKeyInfo includes a signature that proves to the client that the server has accepted the proofOfOwnership (ISO 14229-1:2020).. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related Related requirements: RFQX-CVS31-0055
Source document: source document page 14
Related architecture/security element: Key and Certificate Management
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-PKI-04

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: For obvious reasons, the sessionKeyInfo in the ProofOfOwnershipres is not included, in the “concatenation” (see pseudo code above) when the signature is being calculated.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related Related requirements: RFQX-CVS31-0057
Source document: source document page 14
Related architecture/security element: Key and Certificate Management
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-PKI-05

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: H0 hash value is calculated as part of proofOfOwnershipServer in verifyCertificateBidirectional response.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related Related requirements: RFQX-CVS31-0127
Source document: source document page 21
Related architecture/security element: Key and Certificate Management
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-PKI-06

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: Removed AUTH_REQ 137 since it is covered by AUTH_REQ 135 Removed in Annex A the reference to verifyCertificatesUniDirectional since it is not supported. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related Related requirements: RFQX-CVS31-0164
Source document: source document page 29
Related architecture/security element: Key and Certificate Management
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-PKI-07

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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 into. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related Related requirements: RFQX-CVS31-0197
Source document: source document page 29
Related architecture/security element: Key and Certificate Management
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-PKI-08

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: Removed in Annex A the reference to verifyCertificatesUniDirectional since it is not supported. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related Related requirements: RFQX-CVS31-0211
Source document: source document page 29
Related architecture/security element: Key and Certificate Management
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-PKI-09

Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: Added Chapter 2.1.1.2 lengthOfCertificateClient Added. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related Related requirements: RFQX-CVS31-0246
Source document: source document page 30
Related architecture/security element: Key and Certificate Management
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

Hardware Security / HSM

CQ-HSM-01

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 2*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). This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Architecture
Workshop Block: Block 3: Security Concept and Assets
Why it matters: Some security mechanisms require hardware-backed protection.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Software-only assumptions may be unsafe for key protection and platform integrity.
Related Related requirements: RFQX-3299216-1-0147
Source document: source document page 28
Related architecture/security element: Hardware Platform / Secure Boot and Platform Integrity
Recommended owner: Supplier
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-HSM-02

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The server erases the applicable SW identification DIDs, see Erase Memory routine requirements in 8.3.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Architecture
Workshop Block: Block 3: Security Concept and Assets
Why it matters: Some security mechanisms require hardware-backed protection.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Software-only assumptions may be unsafe for key protection and platform integrity.
Related Related requirements: RFQX-CVS123-2-0127
Source document: source document page 17
Related architecture/security element: Hardware Platform / Secure Boot and Platform Integrity
Recommended owner: Supplier
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-HSM-03

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 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.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Architecture
Workshop Block: Block 3: Security Concept and Assets
Why it matters: Some security mechanisms require hardware-backed protection.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Software-only assumptions may be unsafe for key protection and platform integrity.
Related Related requirements: RFQX-CVS123-2-0145
Source document: source document page 19
Related architecture/security element: Hardware Platform / Secure Boot and Platform Integrity
Recommended owner: Supplier
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-HSM-04

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Architecture
Workshop Block: Block 3: Security Concept and Assets
Why it matters: Some security mechanisms require hardware-backed protection.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Software-only assumptions may be unsafe for key protection and platform integrity.
Related Related requirements: RFQX-CVS123-2-0202
Source document: source document page 24
Related architecture/security element: Hardware Platform / Secure Boot and Platform Integrity
Recommended owner: Supplier
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-HSM-05

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Architecture
Workshop Block: Block 3: Security Concept and Assets
Why it matters: Some security mechanisms require hardware-backed protection.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Software-only assumptions may be unsafe for key protection and platform integrity.
Related Related requirements: RFQX-CVS123-2-0257
Source document: source document page 32
Related architecture/security element: Hardware Platform / Secure Boot and Platform Integrity
Recommended owner: Supplier
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-HSM-06

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: For the context of SDSC, range is defined as: • Start = memory address offset to be verified/decrypted.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Architecture
Workshop Block: Block 3: Security Concept and Assets
Why it matters: Some security mechanisms require hardware-backed protection.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Software-only assumptions may be unsafe for key protection and platform integrity.
Related Related requirements: RFQX-CVS123-2-0315
Source document: source document page 40
Related architecture/security element: Hardware Platform / Secure Boot and Platform Integrity
Recommended owner: Supplier
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-HSM-07

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Erased-only bytes are parts of the memory module that are not programmed with data.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Architecture
Workshop Block: Block 3: Security Concept and Assets
Why it matters: Some security mechanisms require hardware-backed protection.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Software-only assumptions may be unsafe for key protection and platform integrity.
Related Related requirements: RFQX-CVS123-2-0332
Source document: source document page 41
Related architecture/security element: Hardware Platform / Secure Boot and Platform Integrity
Recommended owner: Supplier
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-HSM-08

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: #00BFFFFF #008B0000 #0092FFFF Module hashData #00AFAAAA #00AFAAAB Figure 8 – Memory layout. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Architecture
Workshop Block: Block 3: Security Concept and Assets
Why it matters: Some security mechanisms require hardware-backed protection.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Software-only assumptions may be unsafe for key protection and platform integrity.
Related Related requirements: RFQX-CVS123-2-0348
Source document: source document page 47
Related architecture/security element: Hardware Platform / Secure Boot and Platform Integrity
Recommended owner: Supplier
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

Backend / SecOps Ownership

CQ-BACKEND-02

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: 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.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P2
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Blocks implementation planning
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS123-2-0055
Source document: source document page 10
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Not Applicable
Rationale: Requirement was not low-confidence in the extracted baseline.
Classification: Needs Customer Clarification

CQ-BACKEND-01

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: CVS40 §5.8 TC-08 Ice water / hot air shock test It is not allowed to use a snorkel to pass this test Y. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-3299216-1-0226
Source document: source document page 43
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-03

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: 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.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS123-2-0093
Source document: source document page 14
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-04

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: Implementation hint: The server resets the “application valid” flag (C1, see CVS124. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS123-2-0125
Source document: source document page 17
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-05

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: , 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).. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS123-2-0138
Source document: source document page 18
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-06

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: , as a part of the consistency check the server verifies the integrity of the programmed software.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS123-2-0141
Source document: source document page 18
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-07

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: As part of the routine checks, the server will use the information defined in SDSC to perform the software verification, see 9.2.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS123-2-0144
Source document: source document page 19
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-08

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: The server responds positively to the request before the reset takes place.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS123-2-0148
Source document: source document page 19
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-09

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: 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.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS123-2-0219
Source document: source document page 26
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-10

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: It is server specific the generator polynomial and initial value to be used.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS123-2-0248
Source document: source document page 30
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-11

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: For the context of SDSC, dataLocator is defined as an identification the server uses to locate the software module.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS123-2-0318
Source document: source document page 40
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-12

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: The dataLocator field is used to provide to the server the means to identify which module the verification or encryption entries refer to.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS123-2-0321
Source document: source document page 40
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-13

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: 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.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS151-0017
Source document: source document page 5
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-14

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: 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.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS151-0024
Source document: source document page 6
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-15

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 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.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS151-0026
Source document: source document page 6
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-16

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: When the server is instructed to verify the programmed data, in general the following actions are taken by the server.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS154-0022
Source document: source document page 6
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-17

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: However, the instance specification may state specialized actions: • Server processes each VerificationEntry one by one.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS154-0023
Source document: source document page 6
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-18

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: • Check if the NodeUID of the server is present in the NodeUIDs extension.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS31-0082
Source document: source document page 18
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-19

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: The D-RBACC extension defines client-specific rules that override the role-based access control configuration in the server.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS31-0091
Source document: source document page 18
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-20

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: • 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.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS31-0097
Source document: source document page 19
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-21

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: • The server is reset (i.e server is power cycled).. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS31-0108
Source document: source document page 20
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-22

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: For this requirement, “same client” refers to a request that originates from the same tester address as the tester currently authenticated by the server.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS31-0149
Source document: source document page 23
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-23

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: When a request is received, authenticated or not, the server upon verifying it is from the same client will restart the timer (A3).. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS31-0150
Source document: source document page 23
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BACKEND-24

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: (Changed POO -> proofOfOwnershipServer) Removed. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related Related requirements: RFQX-CVS31-0243
Source document: source document page 30
Related architecture/security element: Backend and IT Systems / Security Operations
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

Logging and Monitoring

CQ-LOG-01

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: In Figure 8, the RBAC complete rule evaluation logic is described.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Security Concept
Workshop Block: Block 3: Security Concept and Assets
Why it matters: Logging and monitoring are evidence and response enablers.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Security events may be unavailable or unusable during incident response.
Related Related requirements: RFQX-CVS151-0076
Source document: source document page 18
Related architecture/security element: Logging and Audit / Security Monitoring
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

Operational Responsibilities

CQ-OPS-01

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: The maximum release stroke is 22,4 mm from FCCP. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Ownership
Workshop Block: Block 5: Ownership and Operations
Why it matters: Lifecycle security depends on clear operational ownership.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Post-release risks may have no owner or evidence path.
Related Related requirements: RFQX-3299216-1-0020
Source document: source document page 8
Related architecture/security element: Operational and Lifecycle Capabilities
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

Tooling / Evidence / Compliance

CQ-EVIDENCE-01

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: A 1. According to ISO 8820-5:2015 SF30 type fuse-links. 2. According to ISO 8820-5:2015 SF51 type fuse-links.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Tooling / Evidence
Workshop Block: Block 5: Ownership and Operations
Why it matters: Customer review needs trustworthy evidence, not only generated reports.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Compliance discussion may stall because evidence authority is unclear.
Related Related requirements: RFQX-3299216-1-0156
Source document: source document page 29
Related architecture/security element: Engineering Toolchain / Compliance Process
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-EVIDENCE-02

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: The software to be received over TransferData (0x36) is to be considered NOT_OK until a verification takes place.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Tooling / Evidence
Workshop Block: Block 5: Ownership and Operations
Why it matters: Customer review needs trustworthy evidence, not only generated reports.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Compliance discussion may stall because evidence authority is unclear.
Related Related requirements: RFQX-CVS123-2-0212
Source document: source document page 25
Related architecture/security element: Engineering Toolchain / Compliance Process
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-EVIDENCE-03

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: The SDSC content, including the reference hash used for software verification, is signed as part of the set request when transmitted over EMP.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Tooling / Evidence
Workshop Block: Block 5: Ownership and Operations
Why it matters: Customer review needs trustworthy evidence, not only generated reports.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Compliance discussion may stall because evidence authority is unclear.
Related Related requirements: RFQX-CVS123-2-0301
Source document: source document page 38
Related architecture/security element: Engineering Toolchain / Compliance Process
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-EVIDENCE-04

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: SDSC supports verification entries, encryption entries and items as defined in DSC.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Tooling / Evidence
Workshop Block: Block 5: Ownership and Operations
Why it matters: Customer review needs trustworthy evidence, not only generated reports.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Compliance discussion may stall because evidence authority is unclear.
Related Related requirements: RFQX-CVS123-2-0314
Source document: source document page 40
Related architecture/security element: Engineering Toolchain / Compliance Process
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-EVIDENCE-05

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: 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 structure. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Tooling / Evidence
Workshop Block: Block 5: Ownership and Operations
Why it matters: Customer review needs trustworthy evidence, not only generated reports.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Compliance discussion may stall because evidence authority is unclear.
Related Related requirements: RFQX-CVS154-0006
Source document: source document page 4
Related architecture/security element: Engineering Toolchain / Compliance Process
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-EVIDENCE-06

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: The VerificationEntry is of ASN.1 type CHOICE, where the choice stipulates the verification strategy for a piece of data.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Tooling / Evidence
Workshop Block: Block 5: Ownership and Operations
Why it matters: Customer review needs trustworthy evidence, not only generated reports.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Compliance discussion may stall because evidence authority is unclear.
Related Related requirements: RFQX-CVS154-0019
Source document: source document page 6
Related architecture/security element: Engineering Toolchain / Compliance Process
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-EVIDENCE-07

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: See 3.2 for the context-specific tag number for the VerificationEntry choices.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Tooling / Evidence
Workshop Block: Block 5: Ownership and Operations
Why it matters: Customer review needs trustworthy evidence, not only generated reports.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Compliance discussion may stall because evidence authority is unclear.
Related Related requirements: RFQX-CVS154-0020
Source document: source document page 6
Related architecture/security element: Engineering Toolchain / Compliance Process
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-EVIDENCE-08

Question: Confirm which party owns the process, infrastructure, or evidence obligation implied by this item: Definition of hashCmp fields: Refer to Figure 3 for type definitions of each field.. This affects supplier work products, customer-owned infrastructure, lifecycle support, and proposal assumptions.
Priority: P3
Decision Type: Tooling / Evidence
Workshop Block: Block 5: Ownership and Operations
Why it matters: Customer review needs trustworthy evidence, not only generated reports.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Compliance discussion may stall because evidence authority is unclear.
Related Related requirements: RFQX-CVS154-0024
Source document: source document page 6
Related architecture/security element: Engineering Toolchain / Compliance Process
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

Clarification Priority Matrix

Generated: 2026-06-23T20:54:39+00:00

Total questions: 472
P1 count: 6
P2 count: 1
P3 count: 465

Questions by Domain

Backend / SecOps Ownership: 24
Diagnostic and Service Access: 94
Hardware Security / HSM: 8
Logging and Monitoring: 1
Network and External Interfaces: 69
Operational Responsibilities: 1
PKI, Keys, Certificates: 9
Product/System Boundary: 244
Software Update / IVD: 14
Tooling / Evidence / Compliance: 8

Questions by Owner

Joint: 464
Supplier: 8

Questions by Impacted Architecture Area

Backend and IT Systems / Security Operations: 24
Diagnostic access boundary / Secure Diagnostics: 94
Engineering Toolchain / Compliance Process: 8
External Interfaces / vehicle network boundary: 69
Hardware Platform / Secure Boot and Platform Integrity: 8
Key and Certificate Management: 9
Logging and Audit / Security Monitoring: 1
Operational and Lifecycle Capabilities: 1
Secure update / IVD architecture: 14
System boundary / item definition: 244

Sequenced Question Register

CQ-BOUNDARY-03

Priority: P1
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-1001379436-P10-000-01-0003

CQ-BOUNDARY-05

Priority: P1
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-1001379436-P10-000-01-0011

CQ-BOUNDARY-127

Priority: P1
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0005

CQ-BOUNDARY-158

Priority: P1
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0246

CQ-BOUNDARY-199

Priority: P1
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS154-0035

CQ-BOUNDARY-201

Priority: P1
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0006

CQ-BACKEND-02

Priority: P2
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS123-2-0055

CQ-BOUNDARY-01

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-1001379436-P10-000-01-0001

CQ-BOUNDARY-02

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-1001379436-P10-000-01-0002

CQ-BOUNDARY-04

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-1001379436-P10-000-01-0006

CQ-BOUNDARY-06

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-1001379436-P10-000-01-0020

CQ-BOUNDARY-07

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-1001379436-P10-000-01-0023

CQ-BOUNDARY-08

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0003

CQ-BOUNDARY-09

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0046

CQ-BOUNDARY-10

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0048

CQ-BOUNDARY-100

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0146

CQ-BOUNDARY-101

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0147

CQ-BOUNDARY-102

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0149

CQ-BOUNDARY-103

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0150

CQ-BOUNDARY-104

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0151

CQ-BOUNDARY-105

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0155

CQ-BOUNDARY-106

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0156

CQ-BOUNDARY-107

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0158

CQ-BOUNDARY-108

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0160

CQ-BOUNDARY-109

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0162

CQ-BOUNDARY-11

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0127

CQ-BOUNDARY-110

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0174

CQ-BOUNDARY-111

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0180

CQ-BOUNDARY-112

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0191

CQ-BOUNDARY-113

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0210

CQ-BOUNDARY-114

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0249

CQ-BOUNDARY-115

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0253

CQ-BOUNDARY-116

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0255

CQ-BOUNDARY-117

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0259

CQ-BOUNDARY-118

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0264

CQ-BOUNDARY-119

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0272

CQ-BOUNDARY-12

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0130

CQ-BOUNDARY-120

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0283

CQ-BOUNDARY-121

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0291

CQ-BOUNDARY-122

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0324

CQ-BOUNDARY-123

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0327

CQ-BOUNDARY-124

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0344

CQ-BOUNDARY-125

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0345

CQ-BOUNDARY-126

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0002

CQ-BOUNDARY-128

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0010

CQ-BOUNDARY-129

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0021

CQ-BOUNDARY-13

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0141

CQ-BOUNDARY-130

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0033

CQ-BOUNDARY-131

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0041

CQ-BOUNDARY-132

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0062

CQ-BOUNDARY-133

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0066

CQ-BOUNDARY-134

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0067

CQ-BOUNDARY-135

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0076

CQ-BOUNDARY-136

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0085

CQ-BOUNDARY-137

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0098

CQ-BOUNDARY-138

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0105

CQ-BOUNDARY-139

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0109

CQ-BOUNDARY-14

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0157

CQ-BOUNDARY-140

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0111

CQ-BOUNDARY-141

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0115

CQ-BOUNDARY-142

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0118

CQ-BOUNDARY-143

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0119

CQ-BOUNDARY-144

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0120

CQ-BOUNDARY-145

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0121

CQ-BOUNDARY-146

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0122

CQ-BOUNDARY-147

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0123

CQ-BOUNDARY-148

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0124

CQ-BOUNDARY-149

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0125

CQ-BOUNDARY-15

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0158

CQ-BOUNDARY-150

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0126

CQ-BOUNDARY-151

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0127

CQ-BOUNDARY-152

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0143

CQ-BOUNDARY-153

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0151

CQ-BOUNDARY-154

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0173

CQ-BOUNDARY-155

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0181

CQ-BOUNDARY-156

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0221

CQ-BOUNDARY-157

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0240

CQ-BOUNDARY-159

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0299

CQ-BOUNDARY-16

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0197

CQ-BOUNDARY-160

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0326

CQ-BOUNDARY-161

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0344

CQ-BOUNDARY-162

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0361

CQ-BOUNDARY-163

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS124-0419

CQ-BOUNDARY-164

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0001

CQ-BOUNDARY-165

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0005

CQ-BOUNDARY-166

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0007

CQ-BOUNDARY-167

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0008

CQ-BOUNDARY-168

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0009

CQ-BOUNDARY-169

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0010

CQ-BOUNDARY-17

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0222

CQ-BOUNDARY-170

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0012

CQ-BOUNDARY-171

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0013

CQ-BOUNDARY-172

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0021

CQ-BOUNDARY-173

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0022

CQ-BOUNDARY-174

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0025

CQ-BOUNDARY-175

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0027

CQ-BOUNDARY-176

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0029

CQ-BOUNDARY-177

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0031

CQ-BOUNDARY-178

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0038

CQ-BOUNDARY-179

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0039

CQ-BOUNDARY-18

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0223

CQ-BOUNDARY-180

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0042

CQ-BOUNDARY-181

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0043

CQ-BOUNDARY-182

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0046

CQ-BOUNDARY-183

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0047

CQ-BOUNDARY-184

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0052

CQ-BOUNDARY-185

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0056

CQ-BOUNDARY-186

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0059

CQ-BOUNDARY-187

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0061

CQ-BOUNDARY-188

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0063

CQ-BOUNDARY-189

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0069

CQ-BOUNDARY-19

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0229

CQ-BOUNDARY-190

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0070

CQ-BOUNDARY-191

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0072

CQ-BOUNDARY-192

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS151-0090

CQ-BOUNDARY-193

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS154-0001

CQ-BOUNDARY-194

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS154-0005

CQ-BOUNDARY-195

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS154-0007

CQ-BOUNDARY-196

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS154-0028

CQ-BOUNDARY-197

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS154-0030

CQ-BOUNDARY-198

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS154-0033

CQ-BOUNDARY-20

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0234

CQ-BOUNDARY-200

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0002

CQ-BOUNDARY-202

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0013

CQ-BOUNDARY-203

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0023

CQ-BOUNDARY-204

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0032

CQ-BOUNDARY-205

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0035

CQ-BOUNDARY-206

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0039

CQ-BOUNDARY-207

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0050

CQ-BOUNDARY-208

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0052

CQ-BOUNDARY-209

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0053

CQ-BOUNDARY-21

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0235

CQ-BOUNDARY-210

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0064

CQ-BOUNDARY-211

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0085

CQ-BOUNDARY-212

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0086

CQ-BOUNDARY-213

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0092

CQ-BOUNDARY-214

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0107

CQ-BOUNDARY-215

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0112

CQ-BOUNDARY-216

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0115

CQ-BOUNDARY-217

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0123

CQ-BOUNDARY-218

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0126

CQ-BOUNDARY-219

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0131

CQ-BOUNDARY-22

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0238

CQ-BOUNDARY-220

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0132

CQ-BOUNDARY-221

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0135

CQ-BOUNDARY-222

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0136

CQ-BOUNDARY-223

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0139

CQ-BOUNDARY-224

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0140

CQ-BOUNDARY-225

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0229

CQ-BOUNDARY-226

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0230

CQ-BOUNDARY-227

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0244

CQ-BOUNDARY-228

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0245

CQ-BOUNDARY-229

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS31-0254

CQ-BOUNDARY-23

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0240

CQ-BOUNDARY-230

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS32-0002

CQ-BOUNDARY-231

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS32-0005

CQ-BOUNDARY-232

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS32-0006

CQ-BOUNDARY-233

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS32-0013

CQ-BOUNDARY-234

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS32-0015

CQ-BOUNDARY-235

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS32-0045

CQ-BOUNDARY-236

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS32-0049

CQ-BOUNDARY-237

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS32-0050

CQ-BOUNDARY-238

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS32-0052

CQ-BOUNDARY-239

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS32-0062

CQ-BOUNDARY-24

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0241

CQ-BOUNDARY-240

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS32-0086

CQ-BOUNDARY-241

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS32-0112

CQ-BOUNDARY-242

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS32-0114

CQ-BOUNDARY-243

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS32-0117

CQ-BOUNDARY-244

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS32-0138

CQ-BOUNDARY-25

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0242

CQ-BOUNDARY-26

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0246

CQ-BOUNDARY-27

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0247

CQ-BOUNDARY-28

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0248

CQ-BOUNDARY-29

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0250

CQ-BOUNDARY-30

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0251

CQ-BOUNDARY-31

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0257

CQ-BOUNDARY-32

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0266

CQ-BOUNDARY-33

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0267

CQ-BOUNDARY-34

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0268

CQ-BOUNDARY-35

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0269

CQ-BOUNDARY-36

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0270

CQ-BOUNDARY-37

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0271

CQ-BOUNDARY-38

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0272

CQ-BOUNDARY-39

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0273

CQ-BOUNDARY-40

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0274

CQ-BOUNDARY-41

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0275

CQ-BOUNDARY-42

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0276

CQ-BOUNDARY-43

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0277

CQ-BOUNDARY-44

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0278

CQ-BOUNDARY-45

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0284

CQ-BOUNDARY-46

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0301

CQ-BOUNDARY-47

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-3299216-1-0309

CQ-BOUNDARY-48

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0001

CQ-BOUNDARY-49

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0005

CQ-BOUNDARY-50

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0006

CQ-BOUNDARY-51

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0007

CQ-BOUNDARY-52

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0009

CQ-BOUNDARY-53

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0012

CQ-BOUNDARY-54

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0015

CQ-BOUNDARY-55

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0016

CQ-BOUNDARY-56

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0017

CQ-BOUNDARY-57

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0025

CQ-BOUNDARY-58

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0027

CQ-BOUNDARY-59

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0033

CQ-BOUNDARY-60

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0045

CQ-BOUNDARY-61

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0054

CQ-BOUNDARY-62

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0060

CQ-BOUNDARY-63

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0063

CQ-BOUNDARY-64

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0073

CQ-BOUNDARY-65

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0074

CQ-BOUNDARY-66

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0080

CQ-BOUNDARY-67

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0081

CQ-BOUNDARY-68

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0082

CQ-BOUNDARY-69

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0084

CQ-BOUNDARY-70

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0086

CQ-BOUNDARY-71

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0087

CQ-BOUNDARY-72

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0089

CQ-BOUNDARY-73

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0090

CQ-BOUNDARY-74

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0091

CQ-BOUNDARY-75

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0096

CQ-BOUNDARY-76

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0098

CQ-BOUNDARY-77

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0099

CQ-BOUNDARY-78

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0100

CQ-BOUNDARY-79

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0101

CQ-BOUNDARY-80

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0102

CQ-BOUNDARY-81

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0103

CQ-BOUNDARY-82

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0104

CQ-BOUNDARY-83

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0106

CQ-BOUNDARY-84

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0107

CQ-BOUNDARY-85

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0108

CQ-BOUNDARY-86

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0111

CQ-BOUNDARY-87

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0113

CQ-BOUNDARY-88

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0115

CQ-BOUNDARY-89

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0116

CQ-BOUNDARY-90

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0117

CQ-BOUNDARY-91

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0118

CQ-BOUNDARY-92

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0122

CQ-BOUNDARY-93

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0129

CQ-BOUNDARY-94

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0130

CQ-BOUNDARY-95

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0131

CQ-BOUNDARY-96

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0132

CQ-BOUNDARY-97

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0133

CQ-BOUNDARY-98

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0139

CQ-BOUNDARY-99

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related Related requirements: RFQX-CVS123-2-0143

CQ-INTERFACE-01

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-3299216-1-0005

CQ-INTERFACE-02

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-3299216-1-0006

CQ-INTERFACE-03

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-3299216-1-0023

CQ-INTERFACE-04

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-3299216-1-0053

CQ-INTERFACE-05

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-3299216-1-0080

CQ-INTERFACE-06

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-3299216-1-0173

CQ-INTERFACE-07

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS123-2-0008

CQ-INTERFACE-08

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS123-2-0085

CQ-INTERFACE-09

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS123-2-0280

CQ-INTERFACE-10

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS123-2-0293

CQ-INTERFACE-11

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS123-2-0346

CQ-INTERFACE-12

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS124-0102

CQ-INTERFACE-13

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS124-0194

CQ-INTERFACE-14

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS124-0301

CQ-INTERFACE-15

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS124-0357

CQ-INTERFACE-16

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS151-0015

CQ-INTERFACE-17

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS151-0064

CQ-INTERFACE-18

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS31-0069

CQ-INTERFACE-19

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS31-0072

CQ-INTERFACE-20

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0010

CQ-INTERFACE-21

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0011

CQ-INTERFACE-22

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0018

CQ-INTERFACE-23

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0022

CQ-INTERFACE-24

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0023

CQ-INTERFACE-25

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0024

CQ-INTERFACE-26

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0032

CQ-INTERFACE-27

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0034

CQ-INTERFACE-28

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0037

CQ-INTERFACE-29

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0038

CQ-INTERFACE-30

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0039

CQ-INTERFACE-31

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0041

CQ-INTERFACE-32

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0042

CQ-INTERFACE-33

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0043

CQ-INTERFACE-34

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0055

CQ-INTERFACE-35

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0060

CQ-INTERFACE-36

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0061

CQ-INTERFACE-37

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0063

CQ-INTERFACE-38

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0067

CQ-INTERFACE-39

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0072

CQ-INTERFACE-40

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0087

CQ-INTERFACE-41

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0089

CQ-INTERFACE-42

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0090

CQ-INTERFACE-43

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0094

CQ-INTERFACE-44

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0097

CQ-INTERFACE-45

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0098

CQ-INTERFACE-46

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0113

CQ-INTERFACE-47

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0115

CQ-INTERFACE-48

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0116

CQ-INTERFACE-49

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0118

CQ-INTERFACE-50

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0127

CQ-INTERFACE-51

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0129

CQ-INTERFACE-52

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0132

CQ-INTERFACE-53

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0134

CQ-INTERFACE-54

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0135

CQ-INTERFACE-55

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0136

CQ-INTERFACE-56

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0137

CQ-INTERFACE-57

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0148

CQ-INTERFACE-58

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0149

CQ-INTERFACE-59

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0150

CQ-INTERFACE-60

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0153

CQ-INTERFACE-61

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0165

CQ-INTERFACE-62

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0169

CQ-INTERFACE-63

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0170

CQ-INTERFACE-64

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0171

CQ-INTERFACE-65

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0181

CQ-INTERFACE-66

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0187

CQ-INTERFACE-67

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0200

CQ-INTERFACE-68

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0202

CQ-INTERFACE-69

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related Related requirements: RFQX-CVS32-0203

CQ-HSM-01

Priority: P3
Workshop Block: Block 3: Security Concept and Assets
Decision Type: Architecture
Domain: Hardware Security / HSM
Recommended owner: Supplier
Impacted architecture/security area: Hardware Platform / Secure Boot and Platform Integrity
Related Related requirements: RFQX-3299216-1-0147

CQ-HSM-02

Priority: P3
Workshop Block: Block 3: Security Concept and Assets
Decision Type: Architecture
Domain: Hardware Security / HSM
Recommended owner: Supplier
Impacted architecture/security area: Hardware Platform / Secure Boot and Platform Integrity
Related Related requirements: RFQX-CVS123-2-0127

CQ-HSM-03

Priority: P3
Workshop Block: Block 3: Security Concept and Assets
Decision Type: Architecture
Domain: Hardware Security / HSM
Recommended owner: Supplier
Impacted architecture/security area: Hardware Platform / Secure Boot and Platform Integrity
Related Related requirements: RFQX-CVS123-2-0145

CQ-HSM-04

Priority: P3
Workshop Block: Block 3: Security Concept and Assets
Decision Type: Architecture
Domain: Hardware Security / HSM
Recommended owner: Supplier
Impacted architecture/security area: Hardware Platform / Secure Boot and Platform Integrity
Related Related requirements: RFQX-CVS123-2-0202

CQ-HSM-05

Priority: P3
Workshop Block: Block 3: Security Concept and Assets
Decision Type: Architecture
Domain: Hardware Security / HSM
Recommended owner: Supplier
Impacted architecture/security area: Hardware Platform / Secure Boot and Platform Integrity
Related Related requirements: RFQX-CVS123-2-0257

CQ-HSM-06

Priority: P3
Workshop Block: Block 3: Security Concept and Assets
Decision Type: Architecture
Domain: Hardware Security / HSM
Recommended owner: Supplier
Impacted architecture/security area: Hardware Platform / Secure Boot and Platform Integrity
Related Related requirements: RFQX-CVS123-2-0315

CQ-HSM-07

Priority: P3
Workshop Block: Block 3: Security Concept and Assets
Decision Type: Architecture
Domain: Hardware Security / HSM
Recommended owner: Supplier
Impacted architecture/security area: Hardware Platform / Secure Boot and Platform Integrity
Related Related requirements: RFQX-CVS123-2-0332

CQ-HSM-08

Priority: P3
Workshop Block: Block 3: Security Concept and Assets
Decision Type: Architecture
Domain: Hardware Security / HSM
Recommended owner: Supplier
Impacted architecture/security area: Hardware Platform / Secure Boot and Platform Integrity
Related Related requirements: RFQX-CVS123-2-0348

CQ-LOG-01

Priority: P3
Workshop Block: Block 3: Security Concept and Assets
Decision Type: Security Concept
Domain: Logging and Monitoring
Recommended owner: Joint
Impacted architecture/security area: Logging and Audit / Security Monitoring
Related Related requirements: RFQX-CVS151-0076

CQ-DIAG-01

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS123-2-0013

CQ-DIAG-02

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS123-2-0026

CQ-DIAG-03

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS123-2-0088

CQ-DIAG-04

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS123-2-0092

CQ-DIAG-05

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS123-2-0097

CQ-DIAG-06

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS123-2-0105

CQ-DIAG-07

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS123-2-0123

CQ-DIAG-08

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS123-2-0124

CQ-DIAG-09

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS123-2-0126

CQ-DIAG-10

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS123-2-0128

CQ-DIAG-11

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS123-2-0136

CQ-DIAG-12

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS123-2-0159

CQ-DIAG-13

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS123-2-0231

CQ-DIAG-14

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS123-2-0290

CQ-DIAG-15

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0022

CQ-DIAG-16

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0026

CQ-DIAG-17

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0035

CQ-DIAG-18

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0047

CQ-DIAG-19

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0052

CQ-DIAG-20

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0090

CQ-DIAG-21

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0091

CQ-DIAG-22

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0095

CQ-DIAG-23

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0096

CQ-DIAG-24

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0097

CQ-DIAG-25

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0099

CQ-DIAG-26

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0100

CQ-DIAG-27

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0101

CQ-DIAG-28

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0103

CQ-DIAG-29

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0106

CQ-DIAG-30

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0107

CQ-DIAG-31

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0108

CQ-DIAG-32

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0110

CQ-DIAG-33

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0112

CQ-DIAG-34

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0113

CQ-DIAG-35

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0114

CQ-DIAG-36

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0116

CQ-DIAG-37

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0136

CQ-DIAG-38

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0170

CQ-DIAG-39

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0188

CQ-DIAG-40

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0189

CQ-DIAG-41

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0190

CQ-DIAG-42

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0191

CQ-DIAG-43

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0200

CQ-DIAG-44

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0208

CQ-DIAG-45

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0211

CQ-DIAG-46

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0214

CQ-DIAG-47

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0218

CQ-DIAG-48

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0231

CQ-DIAG-49

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0261

CQ-DIAG-50

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0262

CQ-DIAG-51

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0271

CQ-DIAG-52

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0286

CQ-DIAG-53

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0293

CQ-DIAG-54

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0342

CQ-DIAG-55

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0358

CQ-DIAG-56

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0359

CQ-DIAG-57

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0360

CQ-DIAG-58

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0363

CQ-DIAG-59

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0394

CQ-DIAG-60

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0395

CQ-DIAG-61

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0401

CQ-DIAG-62

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0411

CQ-DIAG-63

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0413

CQ-DIAG-64

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0422

CQ-DIAG-65

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0423

CQ-DIAG-66

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0424

CQ-DIAG-67

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0425

CQ-DIAG-68

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0426

CQ-DIAG-69

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0428

CQ-DIAG-70

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0429

CQ-DIAG-71

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0430

CQ-DIAG-72

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0451

CQ-DIAG-73

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0452

CQ-DIAG-74

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0454

CQ-DIAG-75

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0455

CQ-DIAG-76

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0456

CQ-DIAG-77

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0460

CQ-DIAG-78

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0461

CQ-DIAG-79

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS124-0465

CQ-DIAG-80

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS151-0067

CQ-DIAG-81

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS151-0077

CQ-DIAG-82

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS31-0018

CQ-DIAG-83

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS31-0044

CQ-DIAG-84

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS31-0076

CQ-DIAG-85

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS31-0116

CQ-DIAG-86

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS31-0118

CQ-DIAG-87

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS31-0129

CQ-DIAG-88

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS31-0130

CQ-DIAG-89

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS31-0144

CQ-DIAG-90

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS31-0145

CQ-DIAG-91

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS31-0159

CQ-DIAG-92

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS31-0161

CQ-DIAG-93

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS31-0249

CQ-DIAG-94

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related Related requirements: RFQX-CVS32-0017

CQ-PKI-01

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: PKI, Keys, Certificates
Recommended owner: Joint
Impacted architecture/security area: Key and Certificate Management
Related Related requirements: RFQX-CVS123-2-0296

CQ-PKI-02

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: PKI, Keys, Certificates
Recommended owner: Joint
Impacted architecture/security area: Key and Certificate Management
Related Related requirements: RFQX-CVS31-0034

CQ-PKI-03

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: PKI, Keys, Certificates
Recommended owner: Joint
Impacted architecture/security area: Key and Certificate Management
Related Related requirements: RFQX-CVS31-0055

CQ-PKI-04

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: PKI, Keys, Certificates
Recommended owner: Joint
Impacted architecture/security area: Key and Certificate Management
Related Related requirements: RFQX-CVS31-0057

CQ-PKI-05

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: PKI, Keys, Certificates
Recommended owner: Joint
Impacted architecture/security area: Key and Certificate Management
Related Related requirements: RFQX-CVS31-0127

CQ-PKI-06

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: PKI, Keys, Certificates
Recommended owner: Joint
Impacted architecture/security area: Key and Certificate Management
Related Related requirements: RFQX-CVS31-0164

CQ-PKI-07

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: PKI, Keys, Certificates
Recommended owner: Joint
Impacted architecture/security area: Key and Certificate Management
Related Related requirements: RFQX-CVS31-0197

CQ-PKI-08

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: PKI, Keys, Certificates
Recommended owner: Joint
Impacted architecture/security area: Key and Certificate Management
Related Related requirements: RFQX-CVS31-0211

CQ-PKI-09

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: PKI, Keys, Certificates
Recommended owner: Joint
Impacted architecture/security area: Key and Certificate Management
Related Related requirements: RFQX-CVS31-0246

CQ-UPDATE-01

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: Software Update / IVD
Recommended owner: Joint
Impacted architecture/security area: Secure update / IVD architecture
Related Related requirements: RFQX-CVS123-2-0004

CQ-UPDATE-02

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: Software Update / IVD
Recommended owner: Joint
Impacted architecture/security area: Secure update / IVD architecture
Related Related requirements: RFQX-CVS123-2-0076

CQ-UPDATE-03

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: Software Update / IVD
Recommended owner: Joint
Impacted architecture/security area: Secure update / IVD architecture
Related Related requirements: RFQX-CVS123-2-0077

CQ-UPDATE-04

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: Software Update / IVD
Recommended owner: Joint
Impacted architecture/security area: Secure update / IVD architecture
Related Related requirements: RFQX-CVS123-2-0083

CQ-UPDATE-05

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: Software Update / IVD
Recommended owner: Joint
Impacted architecture/security area: Secure update / IVD architecture
Related Related requirements: RFQX-CVS123-2-0095

CQ-UPDATE-06

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: Software Update / IVD
Recommended owner: Joint
Impacted architecture/security area: Secure update / IVD architecture
Related Related requirements: RFQX-CVS123-2-0109

CQ-UPDATE-07

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: Software Update / IVD
Recommended owner: Joint
Impacted architecture/security area: Secure update / IVD architecture
Related Related requirements: RFQX-CVS123-2-0119

CQ-UPDATE-08

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: Software Update / IVD
Recommended owner: Joint
Impacted architecture/security area: Secure update / IVD architecture
Related Related requirements: RFQX-CVS123-2-0120

CQ-UPDATE-09

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: Software Update / IVD
Recommended owner: Joint
Impacted architecture/security area: Secure update / IVD architecture
Related Related requirements: RFQX-CVS123-2-0121

CQ-UPDATE-10

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: Software Update / IVD
Recommended owner: Joint
Impacted architecture/security area: Secure update / IVD architecture
Related Related requirements: RFQX-CVS123-2-0134

CQ-UPDATE-11

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: Software Update / IVD
Recommended owner: Joint
Impacted architecture/security area: Secure update / IVD architecture
Related Related requirements: RFQX-CVS123-2-0135

CQ-UPDATE-12

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: Software Update / IVD
Recommended owner: Joint
Impacted architecture/security area: Secure update / IVD architecture
Related Related requirements: RFQX-CVS123-2-0163

CQ-UPDATE-13

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: Software Update / IVD
Recommended owner: Joint
Impacted architecture/security area: Secure update / IVD architecture
Related Related requirements: RFQX-CVS123-2-0170

CQ-UPDATE-14

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Security Concept
Domain: Software Update / IVD
Recommended owner: Joint
Impacted architecture/security area: Secure update / IVD architecture
Related Related requirements: RFQX-CVS123-2-0270

CQ-BACKEND-01

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-3299216-1-0226

CQ-BACKEND-03

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS123-2-0093

CQ-BACKEND-04

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS123-2-0125

CQ-BACKEND-05

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS123-2-0138

CQ-BACKEND-06

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS123-2-0141

CQ-BACKEND-07

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS123-2-0144

CQ-BACKEND-08

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS123-2-0148

CQ-BACKEND-09

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS123-2-0219

CQ-BACKEND-10

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS123-2-0248

CQ-BACKEND-11

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS123-2-0318

CQ-BACKEND-12

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS123-2-0321

CQ-BACKEND-13

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS151-0017

CQ-BACKEND-14

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS151-0024

CQ-BACKEND-15

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS151-0026

CQ-BACKEND-16

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS154-0022

CQ-BACKEND-17

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS154-0023

CQ-BACKEND-18

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS31-0082

CQ-BACKEND-19

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS31-0091

CQ-BACKEND-20

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS31-0097

CQ-BACKEND-21

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS31-0108

CQ-BACKEND-22

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS31-0149

CQ-BACKEND-23

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS31-0150

CQ-BACKEND-24

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Backend / SecOps Ownership
Recommended owner: Joint
Impacted architecture/security area: Backend and IT Systems / Security Operations
Related Related requirements: RFQX-CVS31-0243

CQ-OPS-01

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Ownership
Domain: Operational Responsibilities
Recommended owner: Joint
Impacted architecture/security area: Operational and Lifecycle Capabilities
Related Related requirements: RFQX-3299216-1-0020

CQ-EVIDENCE-01

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Tooling / Evidence
Domain: Tooling / Evidence / Compliance
Recommended owner: Joint
Impacted architecture/security area: Engineering Toolchain / Compliance Process
Related Related requirements: RFQX-3299216-1-0156

CQ-EVIDENCE-02

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Tooling / Evidence
Domain: Tooling / Evidence / Compliance
Recommended owner: Joint
Impacted architecture/security area: Engineering Toolchain / Compliance Process
Related Related requirements: RFQX-CVS123-2-0212

CQ-EVIDENCE-03

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Tooling / Evidence
Domain: Tooling / Evidence / Compliance
Recommended owner: Joint
Impacted architecture/security area: Engineering Toolchain / Compliance Process
Related Related requirements: RFQX-CVS123-2-0301

CQ-EVIDENCE-04

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Tooling / Evidence
Domain: Tooling / Evidence / Compliance
Recommended owner: Joint
Impacted architecture/security area: Engineering Toolchain / Compliance Process
Related Related requirements: RFQX-CVS123-2-0314

CQ-EVIDENCE-05

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Tooling / Evidence
Domain: Tooling / Evidence / Compliance
Recommended owner: Joint
Impacted architecture/security area: Engineering Toolchain / Compliance Process
Related Related requirements: RFQX-CVS154-0006

CQ-EVIDENCE-06

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Tooling / Evidence
Domain: Tooling / Evidence / Compliance
Recommended owner: Joint
Impacted architecture/security area: Engineering Toolchain / Compliance Process
Related Related requirements: RFQX-CVS154-0019

CQ-EVIDENCE-07

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Tooling / Evidence
Domain: Tooling / Evidence / Compliance
Recommended owner: Joint
Impacted architecture/security area: Engineering Toolchain / Compliance Process
Related Related requirements: RFQX-CVS154-0020

CQ-EVIDENCE-08

Priority: P3
Workshop Block: Block 5: Ownership and Operations
Decision Type: Tooling / Evidence
Domain: Tooling / Evidence / Compliance
Recommended owner: Joint
Impacted architecture/security area: Engineering Toolchain / Compliance Process
Related Related requirements: RFQX-CVS154-0024

Customer Workshop Agenda

Duration: 60-90 minutes

Objective

Confirm the product boundary, interfaces, security responsibilities, and evidence expectations needed to move the RFQX package from expert synthesis to customer-review baseline.

Participants

OEM/customer system owner
OEM/customer cybersecurity architect
Supplier system architect
Supplier cybersecurity architect
Diagnostic/update owner
Backend/SecOps or tooling owner where applicable

Pre-read

site/index.html
product_understanding/source document
architecture/source document
cybersecurity/source document
traceability/source document
requirements/source document

Discussion Blocks

1. 10 min: Confirm product/item boundary and customer review objective. 2. 15 min: Review external interfaces, diagnostic access, update/IVD, and PKI/key ownership. 3. 15 min: Review security architecture, assets, trust boundaries, logging, monitoring, backend/SecOps responsibilities. 4. 15 min: Review low-confidence closure and clarify which items are binding, informational, or out of scope. 5. 10 min: Review TARA/residual-risk expectations and approval authority. 6. 5-20 min: Agree actions, owners, and evidence updates.

Decision Points

Accepted item boundary and architecture scope.
Confirmed mandatory security capabilities and optional/reference-only items.
Confirmed owner for each open security and evidence responsibility.
Confirmed next evidence update and review cadence.

Required Outputs

Answered or owner-assigned clarification questions.
Updated architecture assumptions and traceability status.
Customer-approved next-step list for TARA and mechanism allocation.

Follow-up Actions

Update RFQX baseline with customer answers.
Re-run synthesis/site/evidence export.
Move gate from customer-clarification WARN only when decisions are documented.

Low-Confidence Requirement Review

Generated: 2026-06-23T20:54:35+00:00

Low-confidence requirements before review: 803
Active low-confidence requirements after review: 0
Reviewed low-confidence requirements: 803

Status Summary

Needs Manual Markdown Correction: 338
Reclassified as Assumption: 24
Reclassified as Informational: 441

Reviewed Items

RFQX-1001379436-P10-000-01-0001

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 3
Statement: This 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.

RFQX-1001379436-P10-000-01-0002

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 3
Statement: The 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.

RFQX-1001379436-P10-000-01-0004

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 3
Statement: Abbreviation Description ECU Electronic Control Unit Table 2: Abbreviated terms

RFQX-1001379436-P10-000-01-0006

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 5
Statement: Cybersecurity principles are high level requirements that drive development and refinement of functional and technical cybersecurity requirements.

RFQX-1001379436-P10-000-01-0020

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: The vehicle manufacturer reserves the right to perform penetration testing on the ECU to identify potential vulnerabilities.

RFQX-1001379436-P10-000-01-0023

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 7
Statement: 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.

RFQX-3299216-1-0003

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: The actuator is placed outside of the gearbox

RFQX-3299216-1-0005

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: The actuator will be controlled by a position and speed demand by CAN-bus

RFQX-3299216-1-0006

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: The actuator will be controlled by a position and speed demand by a 1kHz PWM signal on wake up connection

RFQX-3299216-1-0020

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 8
Statement: The maximum release stroke is 22,4 mm from FCCP

RFQX-3299216-1-0023

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 9
Statement: The 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.

RFQX-3299216-1-0046

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 12
Statement: The clutch force acting on the pushrod is defined in Appendix A

RFQX-3299216-1-0048

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 12
Statement: The pushrod position when clutch is at rest and only preload force is applied, will vary randomly within 2 mm (± 1mm from FCCP).

RFQX-3299216-1-0053

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 13
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.

RFQX-3299216-1-0080

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: Req. 6.3.1 to 6.3.5 describe the various control modes that can be requested via CAN (Ref 14.14)

RFQX-3299216-1-0095

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 22
Statement: ).

RFQX-3299216-1-0098

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 23
Statement: Accuracy mode

RFQX-3299216-1-0099

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 23
Statement: Not applicable.

RFQX-3299216-1-0100

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 23
Statement: Feedback from the ECA will also be sent via CAN. Specific error reporting as per req. 6.13. Message contents to be agreed with Traton

RFQX-3299216-1-0108

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 23
Statement: ,req.

RFQX-3299216-1-0127

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 25
Statement: Minimum diagnostic feedback described in req. 6.22.1 - 6.22.11.

RFQX-3299216-1-0128

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 25
Statement: Wrong rotation direction

RFQX-3299216-1-0129

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 25
Statement: Short circuit / open load on the phases

RFQX-3299216-1-0130

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 25
Statement: Motor rotation feedback, short circuit / open load

RFQX-3299216-1-0133

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 26
Statement: P 1 Page 6.22.4 Positions sensor short circuit / open load (if used) 6.22.5 Watchdog error 6.22.6 Low voltage 30 6.22.7 CAN-timeout (stored and sent when possible) 6.22.8 High temperature/current consumption (system needs to indicate abnormal usage that can damage the device), indicate a self-protective mode (if applicable) 6.22.9 Error on temperature sensor 6.22.10 High friction in mechanical system 6.22.11 Other electrical HW error

RFQX-3299216-1-0141

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 27
Statement: Internally stored parameters may be accessible only using supplier defined tools .

RFQX-3299216-1-0147

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 28
Statement: 2*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)

RFQX-3299216-1-0151

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: 6.3mm Tin, Sn ≥3 μm thick. ≥1 µm Ni

RFQX-3299216-1-0152

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: 2.8mm Gold, Au ≥0,8 μm thick. ≥1 µm Ni

RFQX-3299216-1-0155

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Power cable length: - - 2*6000 mm

RFQX-3299216-1-0156

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
Statement: A 1. According to ISO 8820-5:2015 SF30 type fuse-links. 2. According to ISO 8820-5:2015 SF51 type fuse-links.

RFQX-3299216-1-0157

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
Statement: Umax: - - 32/36/48 A Specific test relations TBD

RFQX-3299216-1-0158

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
Statement: CVS41 limits may go below this value. Valid only for ECU and communication function. For clutch actuation see req. 5.13

RFQX-3299216-1-0159

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Figure 133 A 3. Up to 100 kHz

RFQX-3299216-1-0173

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 34
Statement: CAN FD: 4000 - - kbit/s Figure 15 - Reference circuit

RFQX-3299216-1-0197

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 38
Statement: The life length requirement is minimum 3000 operating hours per year for 15 years

RFQX-3299216-1-0222

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 41
Statement: Reduced versions of test procedure II may be agreed and used during various tests.

RFQX-3299216-1-0223

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 43
Statement: CVS40 §5.5 TC-05 Temperature cycle test Tmax.tes= +120°C, Tmin.test=-40°C Y

RFQX-3299216-1-0224

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 43
Statement: CVS40 §5.6 TC-06 Thermal shock Y

RFQX-3299216-1-0225

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 43
Statement: CVS40 §5.7 TC-07 Splash water test Y

RFQX-3299216-1-0226

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 43
Statement: CVS40 §5.8 TC-08 Ice water / hot air shock test It is not allowed to use a snorkel to pass this test Y

RFQX-3299216-1-0227

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 43
Statement: CVS40 §5.9 TC-09 Leakage search test Y

RFQX-3299216-1-0229

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 43
Statement: CVS40 §5.11 TC-11 Corrosion in flowing mixed noxious gas N

RFQX-3299216-1-0230

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 43
Statement: CVS40 §5.12 TC-12 Salt spray test Y

RFQX-3299216-1-0231

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 43
Statement: CVS40 §5.13 TC-13 Dirt spray test TBD

RFQX-3299216-1-0232

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 43
Statement: CVS40 §6.2 TM-01 Resonance search Y

RFQX-3299216-1-0233

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 43
Statement: CVS40 §6.3 TM-02 Mechanical shock TBD

RFQX-3299216-1-0234

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 43
Statement: CVS40 §6.4 TM-03 Random vibration and thermal cycle P1 Test 2 Y

RFQX-3299216-1-0235

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 43
Statement: CVS40 §6.5 TM-04 Gravel bombardment and impact Y

RFQX-3299216-1-0236

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 43
Statement: CVS40 §6.6 TM-05 External forces Y

RFQX-3299216-1-0237

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 43
Statement: CVS40 §6.7 TM-06 Drop test – Free fall Y

RFQX-3299216-1-0238

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 43
Statement: CVS40 §7.1 TL-01 Life length As per Chapter 8 Y

RFQX-3299216-1-0239

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 43
Statement: CVS40 §7.2.1 TL-02 Power cycling test Y

RFQX-3299216-1-0240

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 43
Statement: CVS40 §7.2.2 TL-03 Extended thermal shock air TBD

RFQX-3299216-1-0241

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 43
Statement: CVS40 §7.2.3 TL-04 High temperature endurance test TBD

RFQX-3299216-1-0242

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 43
Statement: CVS40 §7.2.4 TL-05 Endurance test / actuation TBD

RFQX-3299216-1-0243

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 44
Statement: CVS40 §7.3 TL-06 Component specific test TBD

RFQX-3299216-1-0244

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 44
Statement: CVS40 §7.4 TL-07 Ageing Y

RFQX-3299216-1-0246

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 44
Statement: CVS40 §8.2 TS-02 UV resistance Datasheet sufficient Y

RFQX-3299216-1-0247

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 44
Statement: CVS40 §8.3 TS-03 Chemical resistance Application method TBD Y

RFQX-3299216-1-0248

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 44
Statement: CVS40 §8.4 TE-01 Isolation resistance and Dielectric strength tests N Exceptions and additional information to CVS41 [Y/N]

RFQX-3299216-1-0249

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 44
Statement: CVS41 §4 Electrical loads Y

RFQX-3299216-1-0250

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 44
Statement: CVS41 §4.1 TE-00 Operating Voltage Class A for ECU and communication. Class B for clutch actuation Y

RFQX-3299216-1-0251

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 44
Statement: CVS41 §4.2 TE-01 Operating Voltage (Long-term overvoltage) Umax: 15 min, functional status Class B Y

RFQX-3299216-1-0252

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 44
Statement: CVS41 §4.3 TE-02 Transient Overvoltage Y

RFQX-3299216-1-0253

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 44
Statement: CVS41 §4.4 TE-03 Transient Undervoltage Y

RFQX-3299216-1-0254

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 44
Statement: CVS41 §4.5 TE-04 Jump start Y

RFQX-3299216-1-0255

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 44
Statement: CVS41 §4.6 TE-05 Load dump, test pulse 5b Y

RFQX-3299216-1-0257

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 47
Statement: CVS46 §4.6.6 Test LFM: Low Frequency Magnetic Y

RFQX-3299216-1-0258

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 47
Statement: CVS46 §4.7 Test VCB CTE N

RFQX-3299216-1-0259

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 47
Statement: CVS46 §4.8 Test VCB AN and VCB CP N

RFQX-3299216-1-0260

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 47
Statement: CVS46 §4.9 Test C-VCB-VCA N

RFQX-3299216-1-0261

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 47
Statement: CVS46 §4.10 Test TSUP VCB A N

RFQX-3299216-1-0262

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 47
Statement: CVS46 §4.11 Test TSUP VCB B N

RFQX-3299216-1-0263

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 47
Statement: CVS46 §4.12 Test VCB Surge N

RFQX-3299216-1-0264

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 47
Statement: CVS46 §4.13 Test VCB Burst N

RFQX-3299216-1-0265

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 47
Statement: CVS46 §4.14 Test VCB Charging mode N

RFQX-3299216-1-0266

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 47
Statement: CVS46 §4.15 Test ESD: Immunity to electrostatic discharge (ESD) Y

RFQX-3299216-1-0267

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 47
Statement: CVS46 §4.15.1 Test ESDD: Direct Discharge, Powered up Y

RFQX-3299216-1-0268

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 47
Statement: CVS46 §4.15.2 Test ESDI: Indirect Discharge (Powered up) Y

RFQX-3299216-1-0269

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 47
Statement: CVS46 §4.15.3 Test ESDH: ESD Handling, Component not energised Y

RFQX-3299216-1-0270

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 47
Statement: CVS46 §5.1 Vehicle test ESD Traton performs Vehicle test, Traton may need support from supplier with any issues originating from the component. Y

RFQX-3299216-1-0271

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 47
Statement: CVS46 §5.2 Vehicle test RE: Emitted interference of the complete vehicle Y

RFQX-3299216-1-0272

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 47
Statement: CVS46 §5.2.1 Vehicle test RE: Protection of receivers outside the vehicle Y

RFQX-3299216-1-0273

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 47
Statement: CVS46 §5.2.2 Vehicle test RE: Self interference Y

RFQX-3299216-1-0274

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 47
Statement: CVS46 §5.3 Vehicle test charging: Vehicle in the AC charging mode N

RFQX-3299216-1-0275

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 47
Statement: CVS46 §5.3.1 Vehicle test: AC charging Vehicle in AC charging mode N

RFQX-3299216-1-0276

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 47
Statement: CVS46 §5.3.2 Vehicle test: DC charging: Vehicle in DC charging mode N

RFQX-3299216-1-0277

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 47
Statement: CVS46 §5.4 Vehicle test RI: Immunity of vehicles to radiated fields Traton performs Vehicle test, Traton may need support from supplier with Y

RFQX-3299216-1-0278

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 47
Statement: CVS46 §5.4.1 Vehicle test RI: External interference sources Y

RFQX-3299216-1-0284

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 50
Statement: Field test Traton will perform field tests with the unit mounted in trucks

RFQX-3299216-1-0301

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 52
Statement: Unless otherwise stated, valid version is the latest available as of 1st May 2026.

RFQX-3299216-1-0307

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 59
Statement: ,

RFQX-3299216-1-0308

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 59
Statement: Normal operation, Class A

RFQX-3299216-1-0309

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 61
Statement: This needs to be checked with the first test run and if necessary the test cycle used in profile B needs to be changed.

RFQX-CVS123-2-0001

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 1
Statement: 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.

RFQX-CVS123-2-0004

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: This document specifies the method to perform software download using Software Update Variant 2 (SUV2).

RFQX-CVS123-2-0005

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: The vehicle manufacturer implementation of the Authentication service (0x29) is defined in CVS31 and SecuredDataTransmission service (0x84) is defined in CVS32.

RFQX-CVS123-2-0006

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: 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.

RFQX-CVS123-2-0007

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: 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.

RFQX-CVS123-2-0008

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: 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.

RFQX-CVS123-2-0009

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: 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.

RFQX-CVS123-2-0012

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: This specification targets ECUs, not clients.

RFQX-CVS123-2-0013

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: Clients may prefer to implement programming support using other service parameter values or even another set of programming steps than

RFQX-CVS123-2-0015

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 5
Statement: The target readers of this specification are ECU suppliers, which can be either internal or external in relation to the vehicle manufacturer.

RFQX-CVS123-2-0016

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 5
Statement: 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.

RFQX-CVS123-2-0017

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 5
Statement: 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 Definition

RFQX-CVS123-2-0018

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 6
Statement: Several terms that are used in this document but not defined in Table 1 are defined by ISO or in the document CVS124.

RFQX-CVS123-2-0025

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: 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.

RFQX-CVS123-2-0026

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: C2 Also referred to as “programming request” flag.

RFQX-CVS123-2-0027

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: 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.

RFQX-CVS123-2-0028

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 6
Statement: C3 Also referred to as “reprogrammed” flag.

RFQX-CVS123-2-0031

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 7
Statement: 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 memory

RFQX-CVS123-2-0032

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 8
Statement: Requirements are prefixed “SUV2_REQ”.

RFQX-CVS123-2-0033

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 8
Statement: Similarly, informative text is prefixed “SUV2_INFO”.

RFQX-CVS123-2-0038

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 9
Statement: If as a deviation with respect to

RFQX-CVS123-2-0045

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 9
Statement: 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.

RFQX-CVS123-2-0054

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 10
Statement: The “boot parameter module” permits a generic bootloader to be an ECU application platform (ECU HW + boot loader software).

RFQX-CVS123-2-0057

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 11
Statement: For definition of DID 0xF197 see CVS124.

RFQX-CVS123-2-0060

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 11
Statement: A joint use of program code for communication functions (com stack) by the application and the boot loader is not permitted.

RFQX-CVS123-2-0063

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 11
Statement: 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.

RFQX-CVS123-2-0073

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 12
Statement: If a valid application is present in the ECU, some of the services described in the programming sequence will be executed in the application.

RFQX-CVS123-2-0074

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 12
Statement: 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.

RFQX-CVS123-2-0076

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 12
Statement: 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).

RFQX-CVS123-2-0077

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 12
Statement: Programming phase #1 is defined to program a server (e.g., download of application software, application data or boot software).

RFQX-CVS123-2-0080

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 12
Statement: For further information on the service details and programming messages structure regarding the SecuredDataTransmission (0x84) service, refer to CVS32.

RFQX-CVS123-2-0081

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 13
Statement: The sequence shown in the following figure shows the Pre-Programming step of phase #1.

RFQX-CVS123-2-0082

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: When this step is entered, the ECU is assumed to be in a state which enables it to receive UDS service requests.

RFQX-CVS123-2-0083

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: For each server in the network, depending on whether an application has been successfully flashed before, it will run in application or boot mode.

RFQX-CVS123-2-0084

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: The client posts a functionally addressed DiagnosticSessionControl (0x10) service request with sessionType equal to DefaultSession and the SPRMIB not set.

RFQX-CVS123-2-0085

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: If servers which support wake-up on CAN are not awake before, this request causes them to wake-up.

RFQX-CVS123-2-0086

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: All servers available on the network and their diagnostic addresses are identified from the positive responses to this request.

RFQX-CVS123-2-0087

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: The client then posts physically or functionally addressed ReadDataByIdentifier (0x22) service requests to collect additional identification data from each identified server.

RFQX-CVS123-2-0088

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: The client post physically addressed RoutineControl (0x31) (EMP) service request with SPRMIB not set and operation-type set to Get (0x01).

RFQX-CVS123-2-0089

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: 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.

RFQX-CVS123-2-0090

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: 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.

RFQX-CVS123-2-0091

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: For reference on EMP control routine, see CVS33.

RFQX-CVS123-2-0092

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: The client post physically addressed RoutineControl (0x31) (EMP) service request with SPRMIB not set and operation-type set to Set (0x00).

RFQX-CVS123-2-0093

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: 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.

RFQX-CVS123-2-0095

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: Alternatively, it may be a client strategy to always update certain entities prior to a software update.

RFQX-CVS123-2-0096

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: For reference on EMP control routine, see CVS33.

RFQX-CVS123-2-0097

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: The client post physically addressed authentication sequence based on CVS31 with SPRMIB not set.

RFQX-CVS123-2-0098

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: The client posts a functionally addressed DiagnosticSessionControl (0x10) service request with sessionType equal to extended diagnostic session and the SPRMIB set.

RFQX-CVS123-2-0099

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: 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.

RFQX-CVS123-2-0100

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: 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.

RFQX-CVS123-2-0101

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: 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).

RFQX-CVS123-2-0102

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: 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.

RFQX-CVS123-2-0103

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: 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.

RFQX-CVS123-2-0104

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: 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.

RFQX-CVS123-2-0105

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: 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.

RFQX-CVS123-2-0106

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: 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.

RFQX-CVS123-2-0107

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: 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.

RFQX-CVS123-2-0108

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: 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.

RFQX-CVS123-2-0109

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 16
Statement: The sequence in Figure 3 shows the programming step of phase #1.

RFQX-CVS123-2-0111

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 16
Statement: The information to verify integrity of the software is contained in software data security container (SDSC), which is transmitted in P1PreB step.

RFQX-CVS123-2-0113

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 16
Statement: If SDSC dictates decryption, the decryption keys are contained in software data security container (SDSC) which is transmitted in P1PreB step.

RFQX-CVS123-2-0115

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
Statement: The client posts a physically addressed DiagnosticSessionControl (0x10) service request with sub-function parameter diagnosticSessionType set to ProgrammingSession and the SPRMIB not set.

RFQX-CVS123-2-0116

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
Statement: If CommunicationControl has not been previously called in the Extended Diagnostic Session the server rejects the request with negative response code NRC 0x22 (conditionsNotCorrect).

RFQX-CVS123-2-0117

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
Statement: Implementation hint: If the server is executing the application the server sets a “programming request” flag (C2, see section Boot software session requirements).

RFQX-CVS123-2-0118

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
Statement: 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.

RFQX-CVS123-2-0119

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
Statement: The boot manager notes the programming request and starts the boot loader.

RFQX-CVS123-2-0120

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
Statement: Implementation hint: The boot manager recognizes the programming request by checking the “programming request” flag (C2).

RFQX-CVS123-2-0121

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
Statement: Implementation hint: The boot manager or the boot loader resets the “programming request” flag (C2).

RFQX-CVS123-2-0122

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
Statement: Finally, the boot loader sends a positive response.

RFQX-CVS123-2-0123

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
Statement: The client post physically addressed authentication sequence based on Authenticate 0x29 with SPRMIB not set.

RFQX-CVS123-2-0124

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
Statement: 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.

RFQX-CVS123-2-0125

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
Statement: Implementation hint: The server resets the “application valid” flag (C1, see CVS124

RFQX-CVS123-2-0126

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
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.

RFQX-CVS123-2-0127

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
Statement: The server erases the applicable SW identification DIDs, see Erase Memory routine requirements in 8.3.

RFQX-CVS123-2-0128

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
Statement: The client posts physically addressed RequestDownload (0x34) service requests with the SPRMIB not set.

RFQX-CVS123-2-0129

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: 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.

RFQX-CVS123-2-0130

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: 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.

RFQX-CVS123-2-0131

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: 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.

RFQX-CVS123-2-0132

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: 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.

RFQX-CVS123-2-0133

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: 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.

RFQX-CVS123-2-0134

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: It is client specific if P1Pro10 will be sent as part of programming phase #1.

RFQX-CVS123-2-0135

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: 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.

RFQX-CVS123-2-0136

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: The client posts a physically addressed RoutineControl (0x31) (checkMemory) service request with the SPRMIB not set.

RFQX-CVS123-2-0137

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 18
Statement: According to

RFQX-CVS123-2-0138

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
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).

RFQX-CVS123-2-0139

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: The response of this routineIdentifier allows the client to identify if the specific transferred block is corrupted.

RFQX-CVS123-2-0140

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 18
Statement: According to

RFQX-CVS123-2-0141

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: , as a part of the consistency check the server verifies the integrity of the programmed software.

RFQX-CVS123-2-0142

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 18
Statement: According to

RFQX-CVS123-2-0143

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
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.

RFQX-CVS123-2-0144

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 19
Statement: As part of the routine checks, the server will use the information defined in SDSC to perform the software verification, see 9.2.

RFQX-CVS123-2-0145

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 19
Statement: 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.

RFQX-CVS123-2-0146

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 19
Statement: The sequence shown in the following figure shows the post-programming step of phase #1.

RFQX-CVS123-2-0147

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 19
Statement: 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.

RFQX-CVS123-2-0148

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 19
Statement: The server responds positively to the request before the reset takes place.

RFQX-CVS123-2-0149

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 19
Statement: 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 programming

RFQX-CVS123-2-0150

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: The application reads and applies the boot parameter values from the boot parameter module.

RFQX-CVS123-2-0151

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: 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.

RFQX-CVS123-2-0155

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: 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.

RFQX-CVS123-2-0156

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: 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.

RFQX-CVS123-2-0157

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 20
Statement: According to

RFQX-CVS123-2-0158

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: , the client post physically addressed authentication (0x29) request with subfunction deAuthenticate (0x00) based on CVS31 with SPRMIB not set.

RFQX-CVS123-2-0159

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: The client post physically addressed RoutineControl (0x31) (EMP) service request with SPRMIB not set and operation-type set to Set (0x00).

RFQX-CVS123-2-0160

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: In this step, it is client dependent if and what entities are relevant to be set after updating the software.

RFQX-CVS123-2-0162

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: For reference on EMP control routine, see CVS33.

RFQX-CVS123-2-0163

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: The programming phase #2 (server configuration or also known as parametrization) as defined in ISO 14229-2 is defined in CVS36.

RFQX-CVS123-2-0170

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 21
Statement: This is to keep the programming time to a minimum.

RFQX-CVS123-2-0171

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 21
Statement: If the performance requirements

RFQX-CVS123-2-0172

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 21
Statement: or

RFQX-CVS123-2-0174

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 21
Statement: This is to shorten the time for the data transfer from the tester to the ECU to be programmed.

RFQX-CVS123-2-0180

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 21
Statement: 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.

RFQX-CVS123-2-0191

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 22
Statement: 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.

RFQX-CVS123-2-0194

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 22
Statement: In case of divergences between CVS124 and Table 3, this document takes precedence.

RFQX-CVS123-2-0195

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 22
Statement: For a server, it is the combination of services support in CVS124 and Table 3 that will constitute the complete picture of supported services.

RFQX-CVS123-2-0202

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 24
Statement: 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.

RFQX-CVS123-2-0208

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 25
Statement: For more information on SDSC, see chapter 9.

RFQX-CVS123-2-0210

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 25
Statement: If an encryptionEntry match is found, see chapter 9.3.

RFQX-CVS123-2-0212

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 25
Statement: The software to be received over TransferData (0x36) is to be considered NOT_OK until a verification takes place.

RFQX-CVS123-2-0219

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 26
Statement: 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.

RFQX-CVS123-2-0221

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 27
Statement: Negative Response

RFQX-CVS123-2-0231

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 28
Statement: 7.3.4 Service 0x37 Parameters 7.3.4.1 Parameter transferRequestParameterRecord

RFQX-CVS123-2-0236

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Negative Response

RFQX-CVS123-2-0245

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: 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.

RFQX-CVS123-2-0248

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
Statement: It is server specific the generator polynomial and initial value to be used.

RFQX-CVS123-2-0249

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 31
Statement: 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 Request

RFQX-CVS123-2-0252

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 31
Statement: 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 Response

RFQX-CVS123-2-0253

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 32
Statement: SUV2_REQ 4 prevents the scenario of erasing the copied bootloader while boot loader update and leaving the ECU without any bootloader.

RFQX-CVS123-2-0255

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 32
Statement: This RoutineIdentifier value allows the client to start a routine which erases ECU internal non- volatile memory.

RFQX-CVS123-2-0257

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 32
Statement: 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.

RFQX-CVS123-2-0259

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 32
Statement: prevents the scenario of erasing the copied bootloader while boot loader update and leaving the ECU without any bootloader.

RFQX-CVS123-2-0264

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 34
Statement: 8.3.4 Routine 0xFF00 Parameters 8.3.4.1 Parameter addressAndLengthFormatIdentifier

RFQX-CVS123-2-0267

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 34
Statement: .

RFQX-CVS123-2-0270

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 35
Statement: This RoutineIdentifier value allows the client to start a consistency check of the server.

RFQX-CVS123-2-0272

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 35
Statement: The client may opt to execute this routineIdentifier as a standalone procedure to check to perform a software consistency check.

RFQX-CVS123-2-0280

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 35
Statement: Details over the integrity check can be found on chapter 9.2.

RFQX-CVS123-2-0283

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 36
Statement: 8.4.4 Routine 0xFF01 Parameters 8.4.4.1 Parameter routineStatus routineResult

RFQX-CVS123-2-0287

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 37
Statement: • Routine 0xFF00 Erase Memory

RFQX-CVS123-2-0288

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 37
Statement: • Service 0x34 RequestDownload

RFQX-CVS123-2-0289

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 37
Statement: • Service 0x36 TransferData

RFQX-CVS123-2-0290

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 37
Statement: • Service 0x37 RequestTransferExit 8.4.4.2 Parameter routineResultProofLength

RFQX-CVS123-2-0291

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 37
Statement: This parameter consist of the length of the routineResultProof parameter.

RFQX-CVS123-2-0293

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 37
Statement: The receipt number is received as part of the EMP message whenever a SDSC is set, please refer to CVS34.

RFQX-CVS123-2-0296

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 37
Statement: For information on receipt-keys, please refer to CVS34.

RFQX-CVS123-2-0300

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 38
Statement: SDSC is transmitted via EMP, see chapter 9.

RFQX-CVS123-2-0301

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 38
Statement: The SDSC content, including the reference hash used for software verification, is signed as part of the set request when transmitted over EMP.

RFQX-CVS123-2-0304

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 38
Statement: • Service 0x34 RequestDownload

RFQX-CVS123-2-0305

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 38
Statement: • Service 0x36 TransferData

RFQX-CVS123-2-0306

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 38
Statement: • Service 0x37 RequestTransferExit

RFQX-CVS123-2-0307

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 39
Statement: Negative Response

RFQX-CVS123-2-0314

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 40
Statement: SDSC supports verification entries, encryption entries and items as defined in DSC.

RFQX-CVS123-2-0315

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 40
Statement: For the context of SDSC, range is defined as: • Start = memory address offset to be verified/decrypted.

RFQX-CVS123-2-0318

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 40
Statement: For the context of SDSC, dataLocator is defined as an identification the server uses to locate the software module.

RFQX-CVS123-2-0321

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 40
Statement: The dataLocator field is used to provide to the server the means to identify which module the verification or encryption entries refer to.

RFQX-CVS123-2-0324

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 41
Statement: In DSC sanity check, there is a specific area of application sanity check which depends on the context of the general DSC.

RFQX-CVS123-2-0327

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 41
Statement: The referenceHash defines the reference hash value to be used in the hash comparison.

RFQX-CVS123-2-0332

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 41
Statement: Erased-only bytes are parts of the memory module that are not programmed with data.

RFQX-CVS123-2-0344

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 42
Statement: The received data to decrypt may only be parts of a software module and it will be based on the range defined.

RFQX-CVS123-2-0345

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 42
Statement: EncryptionEntries are not present if software is not encrypted.

RFQX-CVS123-2-0346

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 42
Statement: The Non-volatile server memory programming complete flow can be found in Annex B.

RFQX-CVS123-2-0347

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 47
Statement: #008AFFFF #

RFQX-CVS123-2-0348

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 47
Statement: #00BFFFFF #008B0000 #0092FFFF Module hashData #00AFAAAA #00AFAAAB Figure 8 – Memory layout

RFQX-CVS124-0002

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 2
Statement: Foreword This CVS124 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable.

RFQX-CVS124-0006

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 6
Statement: Table 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

RFQX-CVS124-0010

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: May This word, or the adjective “Optional”, means that an item is truly optional.

RFQX-CVS124-0020

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 8
Statement: 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 ● ● - - - SUPPLIER

RFQX-CVS124-0021

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 9
Statement: SUPPLIER in the Changing column means that the DID can be changed only at the supplier premises for non-programmable ECUs. Data identifier details.

RFQX-CVS124-0022

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 9
Statement: The format in the DID description in the following tables is given in ODX base data types.

RFQX-CVS124-0023

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 10
Statement: Table 6 – Description of DID 0xF180 bootSoftwareIdentificationDataIdentifier 0xF180 Name : bootSoftwareIdentificationDataIdentifier Byte

RFQX-CVS124-0025

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 10
Statement: 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 0x20

RFQX-CVS124-0026

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 11
Statement: 5.2.1.3 DID 0xF182 applicationDataIdentificationDataIdentifier

RFQX-CVS124-0027

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 11
Statement: 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 .

RFQX-CVS124-0029

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 11
Statement: 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 0x01

RFQX-CVS124-0030

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 12
Statement: 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 0x20

RFQX-CVS124-0032

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 12
Statement: Table 11 – Description of DID 0xF188 vehicleManufacturerECUSoftwareNumberDataIdentifier 0xF188 Name: vehicleManufacturerECUSoftwareNumberDataIdentifier Byte Data #1 : #13 Vehicle manufacturer ECU (server) software number : M : M : 0x20

RFQX-CVS124-0033

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 12
Statement: 5.2.1.7 DID 0xF189 vehicleManufacturerECUSoftwareVersionNumberDataIdentifier

RFQX-CVS124-0034

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 12
Statement: Table 12 – Description of DID 0xF189 vehicleManufacturerECUSoftwareVersionNumberDataIdentifier 0xF189 Name: vehicleManufacturerECUSoftwareVersionNumberDataIdentifier Byte Data

RFQX-CVS124-0035

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 13
Statement: 5.2.1.8 DID 0xF18A systemSupplierIdentifierDataIdentifier

RFQX-CVS124-0037

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 13
Statement: Table 14 – Description of DID 0xF18B ECUManufacturingDateDataIdentifier 0xF18B Name: ECUManufacturingDateDataIdentifier Byte Data #1 .

RFQX-CVS124-0038

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 14
Statement: Table 15 – Description of DID 0xF18C ECUSerialNumberDataIdentifier 0xF18C Name: ECUSerialNumberDataIdentifier Byte Data

RFQX-CVS124-0040

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 14
Statement: Table 16 – Description of DID 0xF190 VINDataIdentifier 0xF190 Name: VINDataIdentifier Byte Data #1 : #17 VIN number : Byte #17 17-Bytes- M : M : 0x30 .

RFQX-CVS124-0041

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: This identifier is used for follow up and quality check at production and service and for legal reasons if applicable.

RFQX-CVS124-0042

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 14
Statement: Table 17 – Description of DID 0xF191 vehicleManufacturerECUHardwareNumberDataIdentifier 0xF191 Name: vehicleManufacturerECUHardwareNumberDataIdentifier Byte Data

RFQX-CVS124-0044

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 15
Statement: 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 systemSupplierECUHardwareVersionNumberDataIdentifier

RFQX-CVS124-0045

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 15
Statement: 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 systemSupplierECUSoftwareNumberDataIdentifier

RFQX-CVS124-0046

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 15
Statement: Table 20 – Description of DID 0xF194 systemSupplierECUSoftwareNumberDataIdentifier 0xF194 Name: systemSupplierECUSoftwareNumberDataIdentifier Byte No Description Format Cvt Byte Value Data To be specified by the External Supplier

RFQX-CVS124-0047

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 16
Statement: DID 0xF197 systemNameOrEngineTypeDataIdentifier

RFQX-CVS124-0048

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 16
Statement: 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 exhaustRegulationOrTypeApprovalNumberDataIdentifier

RFQX-CVS124-0049

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 16
Statement: 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 systemNameOrEngineTypeDataIdentifier

RFQX-CVS124-0050

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 16
Statement: 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 .

RFQX-CVS124-0052

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
Statement: DID 0xF198 SoftwareItemSemanticDataIdentifiers

RFQX-CVS124-0053

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 17
Statement: Table 25 – Description of DID 0xF199 SoftwareAssemblySemanticDataIdentifier s 0xF199 Name: SoftwareAssemblySemanticDataIdentifiers Byte Data #1 : #3 numberOfModules(m) 3-Byte- A_UINT32 M 0x000001 – 0xFFFFFF 01

RFQX-CVS124-0054

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 18
Statement: 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.

RFQX-CVS124-0055

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 19
Statement: Table 27 – Description of DID 0xF19D ECUInstallationDateDataIdentifier 0xF19D Name: ECUInstallationDateDataIdentifier Byte Data

RFQX-CVS124-0056

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 19
Statement: 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 engineNumber

RFQX-CVS124-0057

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 19
Statement: 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 solutions

RFQX-CVS124-0059

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 20
Statement: 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 stamp

RFQX-CVS124-0061

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 20
Statement: 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.

RFQX-CVS124-0062

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: The current date as received on CAN or other ECU-external source at first reception of a valid signal after a software update.

RFQX-CVS124-0063

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 21
Statement: Table 32 – Description of DID 0xF1AB Date at software update stamp 0xF1AB Name: dateAtSoftwareUpdateStamp Byte Data

RFQX-CVS124-0064

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 21
Statement: 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 NodeUID

RFQX-CVS124-0065

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 21
Statement: Table 34 – Description of DID 0xF1AF NodeUID 0xF1AF Name: NodeUID Byte Data #1 : #8 NodeUID 8-Bytes- A_BYTEFIELD M : M : 0x00 : 0x00

RFQX-CVS124-0066

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 22
Statement: This identifier is used to link a ECU HW to its specialized security attributes.

RFQX-CVS124-0067

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 22
Statement: The value to be stored is fetched from TRATON backend system in production.

RFQX-CVS124-0068

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 22
Statement: Table 35 – Description of DID 0xF1B9 RBACCIdentifierNumber 0xF1B9 Name: RBACCIdentifierNumber Byte Data #1 : #16 RBACC Identifier Number 16-Bytes- A_BYTEFIELD M : M : 0x00 : 0x00

RFQX-CVS124-0069

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 22
Statement: Information on RBACC can be found in CVS151.

RFQX-CVS124-0070

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 22
Statement: Table 36 – Description of DID 0xF1BA RBACCStructureVersion 0xF1BA Name: RBACCStructureVersion Byte Data #1 : #2 RBACC Structure Version 2-Bytes- A_BYTEFIELD M : M : 0x00 : 0x00

RFQX-CVS124-0071

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 22
Statement: Information on RBACC can be found in CVS151.

RFQX-CVS124-0072

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 22
Statement: Table 37 – Description of DID 0xF1D1 RootCertificateIdentifier 0xF1D1 Name: RootCertificateIdentifier Byte Data

RFQX-CVS124-0073

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 23
Statement: 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 : Project

RFQX-CVS124-0076

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 23
Statement: The default diagnostic session is referred to as “defaultSession”.

RFQX-CVS124-0080

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 24
Statement: Table 39 – Diagnostic service support Service according to ISO 14229-1 Addressin g mode Application Boot loader

RFQX-CVS124-0085

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 25
Statement: Diagnostics safe state is the following conditions that needs be satisfied to ensure vehicle is not in operation while performing certain diagnostics services.

RFQX-CVS124-0090

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 27
Statement: . Default transition for the start of the software in the server after power-up/wake-up.

RFQX-CVS124-0091

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 27
Statement: Description of the individual transitions as per Figure 2 -State Diagram is explained from

RFQX-CVS124-0092

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 27
Statement: to

RFQX-CVS124-0093

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 27
Statement: .

RFQX-CVS124-0094

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: . The initialization routine is started.

RFQX-CVS124-0095

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 28
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.

RFQX-CVS124-0096

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 28
Statement: . If a programming request is active (progRequest P2 == true), the server activates the programming session in the bootloader module.

RFQX-CVS124-0097

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 28
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.

RFQX-CVS124-0098

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 28
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

RFQX-CVS124-0099

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 28
Statement: . If the client requests a change to the ExtendedSession in the DefaultSession in the application software, the session is changed.

RFQX-CVS124-0100

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 28
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.

RFQX-CVS124-0101

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 28
Statement: . If the client requests a change to the DefaultSession in the ExtendedSession in the application software, the session is changed.

RFQX-CVS124-0102

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 28
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.

RFQX-CVS124-0103

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 28
Statement: . If the client requests a change to the ExtendedSession in ExtendedSession in the application software, the server accepts the request.

RFQX-CVS124-0104

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: 2.

RFQX-CVS124-0105

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
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.

RFQX-CVS124-0106

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
Statement: . If the client requests a change to the DefaultSession in the boot loader ExtendedSession or ProgrammingSession, the reset is performed.

RFQX-CVS124-0107

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
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.

RFQX-CVS124-0108

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
Statement: . If the client requests a change to the DefaultSession in the DefaultSession in the boot loader, the server accepts the request.

RFQX-CVS124-0109

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
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.

RFQX-CVS124-0110

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
Statement: . If the client requests the ExtendedSession in the DefaultSession in the boot loader, the session is changed.

RFQX-CVS124-0111

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
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).

RFQX-CVS124-0112

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
Statement: . If the client requests the ExtendedSession in the ExtendedSession in the boot loader, the server accepts the request.

RFQX-CVS124-0113

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
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.

RFQX-CVS124-0114

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
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.

RFQX-CVS124-0115

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
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).

RFQX-CVS124-0116

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
Statement: . If the client requests the DefaultSession in the DefaultSession in the application, the server accepts the request.

RFQX-CVS124-0117

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: 12.

RFQX-CVS124-0118

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
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.

RFQX-CVS124-0119

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
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.

RFQX-CVS124-0120

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
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.

RFQX-CVS124-0121

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
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.

RFQX-CVS124-0122

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
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.

RFQX-CVS124-0123

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
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.

RFQX-CVS124-0124

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
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.

RFQX-CVS124-0125

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
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.

RFQX-CVS124-0126

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
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.

RFQX-CVS124-0127

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
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.

RFQX-CVS124-0128

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: 24.

RFQX-CVS124-0131

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 31
Statement: 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.

RFQX-CVS124-0136

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 32
Statement: 5.5.1.1.1 Request parameter diagnosticSessionType

RFQX-CVS124-0139

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 32
Statement: Table 43 – Service 0x10 request parameter diagnosticSessionType description Hex (bit 6-0) Description Cvt 0x01 defaultSession M 0x02 ProgrammingSession M 0x03 extendedDiagnosticSession M

RFQX-CVS124-0143

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 32
Statement: Its upto the ECU to include the conditions that are relevant for that particular ECU, but needs to be agreed with Vehicle Manufacturer.

RFQX-CVS124-0144

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 33
Statement: Positive response

RFQX-CVS124-0148

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 33
Statement: 5.5.2 ECUReset (0x11) service

RFQX-CVS124-0151

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 33
Statement: 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.

RFQX-CVS124-0155

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 34
Statement: 5.5.2.1.1 Request parameter resetType

RFQX-CVS124-0156

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 34
Statement: 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 key

RFQX-CVS124-0164

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 34
Statement: Table 45 – Service 0x11 positive response parameter description 1 ECUReset Response SID M 2 resetType M

RFQX-CVS124-0166

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 35
Statement: 5.5.2.3.1 Supported negative response codes

RFQX-CVS124-0167

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 35
Statement: Table 46 – Service 0x11 negative response codes NRC Description and scenario 0x12 sub-functionNotSupported Refer to ISO 14229-1 for scenario.

RFQX-CVS124-0170

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 35
Statement: This requirement mitigates DOS (Denial Of Service) attacks

RFQX-CVS124-0173

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 35
Statement: After receiving CommunicationControl service request, ECUs could still keep sending some networks messages/signals to keep a healthy vehicle system.

RFQX-CVS124-0174

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 36
Statement: Negative response

RFQX-CVS124-0176

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 36
Statement: 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 controlType

RFQX-CVS124-0177

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 36
Statement: 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 communicationType

RFQX-CVS124-0178

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 36
Statement: 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 response

RFQX-CVS124-0179

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 36
Statement: 5.5.3.3 Negative response

RFQX-CVS124-0181

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 37
Statement: A functionally addressed TesterPresent may arrive at any time during another request.

RFQX-CVS124-0183

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 37
Statement: 5.5.4.4 Negative response

RFQX-CVS124-0184

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 37
Statement: 5.5.5 ControlDTCSetting (0x85) service

RFQX-CVS124-0187

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 37
Statement: Refer to ISO 14229-1 for request format.

RFQX-CVS124-0188

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 37
Statement: Refer to ISO 14229-1 for request parameter DTCSettingType.

RFQX-CVS124-0189

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 38
Statement: Request parameter DTCSettingControlOptionRecord

RFQX-CVS124-0190

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 38
Statement: Refer to ISO 14229-1 for positive response format and parameter.

RFQX-CVS124-0191

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 38
Statement: Refer to ISO 14229-1 for negative response format and codes.

RFQX-CVS124-0194

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 38
Statement: Link Control (0x87) service is only applicable to CAN & CAN FD.

RFQX-CVS124-0196

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 39
Statement: Request

RFQX-CVS124-0197

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 39
Statement: 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 linkControlModeIdentifier

RFQX-CVS124-0199

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 39
Statement: 5.5.6.4 Negative Response

RFQX-CVS124-0200

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 39
Statement: 5.5.7 ReadDataByIdentifier (0x22) service 5.5.7.1 Request

RFQX-CVS124-0204

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 40
Statement: Positive response

RFQX-CVS124-0205

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 40
Statement: 5.5.7.3 Negative response

RFQX-CVS124-0206

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 40
Statement: 5.5.8 WriteDataByIdentifier (0x2E) service

RFQX-CVS124-0208

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 40
Statement: The range of a requested dataRecord value has to be checked by the server if the DID is safety relevant.

RFQX-CVS124-0211

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 40
Statement: Additional client requests which start copying RAM buffer data into non-volatile memory are not allowed.

RFQX-CVS124-0214

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 41
Statement: 5.5.9 ClearDiagnosticInformation (0x14) service 5.5.9.1 Request

RFQX-CVS124-0215

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 41
Statement: 5.5.9.1.1 Request parameter groupOfDTC

RFQX-CVS124-0217

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 41
Statement: 5.5.9.3 Negative response

RFQX-CVS124-0218

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 41
Statement: 5.5.10 ReadDTCInformation (0x19) service 5.5.10.1 Request

RFQX-CVS124-0219

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 41
Statement: 5.5.10.1.1 Request parameter reportType

RFQX-CVS124-0220

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 41
Statement: 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 U

RFQX-CVS124-0221

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 42
Statement: Legislated OBD relevant ECUs have to support legislated OBD standards.

RFQX-CVS124-0224

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 42
Statement: 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 M

RFQX-CVS124-0227

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 43
Statement: 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 FunctionalGroupIdentifier

RFQX-CVS124-0231

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 43
Statement: 5.5.10.2.1 Response parameter DTCStatusAvailabilityMask

RFQX-CVS124-0240

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 49
Statement: 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.

RFQX-CVS124-0243

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 51
Statement: 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 DTCExtDataRecord

RFQX-CVS124-0253

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 54
Statement: 5.5.10.3.1 Supported negative response codes

RFQX-CVS124-0255

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 54
Statement: 5.5.11.1.1 Request parameter dataIdentifier

RFQX-CVS124-0257

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 54
Statement: Table 58 – Service 0x2F request parameter controlOptionRecord description 1 inputOutputControlParameter M 2 ..

RFQX-CVS124-0258

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 54
Statement: Table 59 – Service 0x2F request parameter inputOutputControlParameter description 0x00 returnControlToECU Refer to ISO 14229-1 for parameter description.

RFQX-CVS124-0260

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 55
Statement: 5.5.11.3 Negative response

RFQX-CVS124-0261

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 55
Statement: 5.5.12 RoutineControl (0x31) service 5.5.12.1 Request

RFQX-CVS124-0262

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 55
Statement: 5.5.12.1.1 Request parameter RoutineControlType

RFQX-CVS124-0263

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 55
Statement: 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”.

RFQX-CVS124-0266

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 56
Statement: Table 61 – Service 0x31 request parameter RoutineIdentifier description 0x02B2 0x02B3 0x02B4 ReadStatusOfDiagnosticEventCodes

RFQX-CVS124-0268

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 57
Statement: 5.5.12.3 Negative response

RFQX-CVS124-0269

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 57
Statement: 5.5.13 Request Download Service (0x34)

RFQX-CVS124-0271

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 57
Statement: 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.

RFQX-CVS124-0276

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 58
Statement: 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 – 0xF

RFQX-CVS124-0277

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 59
Statement: 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 response

RFQX-CVS124-0278

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 59
Statement: Table 65 – Positive response parameter description #1 RequestDownload Response SID M 0x74 #2 lengthFormatIdentifier M 0x20 #3..

RFQX-CVS124-0279

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 59
Statement: Table 66 – Service 0x34 response parameter lengthFormatIdentifier description 7 - 4 Length (number of bytes) of the maxNumberOfBlockLength parameter M 0x2 3 - 0 ISO reserved.

RFQX-CVS124-0280

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 60
Statement: Table 67 – Service 0x35 request parameter description 1 RequestDownload Request SID M 2 dataFormatIdentifier M 3 addressAndLengthFormatIdentifier M 4 .. (m-1)+4

RFQX-CVS124-0281

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 60
Statement: 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 – 0x1

RFQX-CVS124-0282

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 61
Statement: Request

RFQX-CVS124-0283

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 61
Statement: 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 memoryAddress

RFQX-CVS124-0286

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 61
Statement: 5.5.14.2.1 Response parameter lengthFormatIdentifier

RFQX-CVS124-0287

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 61
Statement: Table 70 – Service 0x35 response parameter lengthFormatIdentifier description 7 - 4 Length (number of bytes) of the maxNumberOfBlockLength parameter M 0x2 3 - 0 ISO reserved.

RFQX-CVS124-0291

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 62
Statement: 5.5.15.3 Negative response

RFQX-CVS124-0292

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 62
Statement: 5.5.15.3.1 Supported negative response codes

RFQX-CVS124-0293

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 62
Statement: 5.5.16 RequestTransferExit (0x37) service 5.5.16.1 Request

RFQX-CVS124-0294

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 62
Statement: Table 71 – Service 0x37 request parameter description 1 RequestTransferExit Request SID M 5.5.16.1.1 Request parameter transferRequestParameterRecord

RFQX-CVS124-0296

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 62
Statement: Table 72 – Service 0x37 positive response parameter description 1 RequestTransferExit Response SID M

RFQX-CVS124-0298

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 63
Statement: 5.5.16.3.1 Supported negative response codes

RFQX-CVS124-0299

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 63
Statement: 5.5.17 SecuredDataTransmission (0x84) service

RFQX-CVS124-0301

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 63
Statement: 5.5.17.1.1 Request message data-parameter definition

RFQX-CVS124-0308

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 64
Statement: Refer to CVS31 .

RFQX-CVS124-0309

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 64
Statement: Refer to CVS31 .

RFQX-CVS124-0310

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 64
Statement: Refer to CVS31 .

RFQX-CVS124-0311

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 64
Statement: 5.5.18.4.1 Supported negative response codes

RFQX-CVS124-0314

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 65
Statement: 5.5.19.2 Request Parameter modeOfOperation

RFQX-CVS124-0322

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 66
Statement: 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 response

RFQX-CVS124-0323

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 66
Statement: 5.5.19.6 Negative response

RFQX-CVS124-0324

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 66
Statement: 5.5.19.7 Supported negative response codes

RFQX-CVS124-0326

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 66
Statement: This RoutineIdentifier enables the client to query the state of the programming preconditions in the server and applicable only for programmable ECUs.

RFQX-CVS124-0335

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 67
Statement: 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-0xFF

RFQX-CVS124-0342

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 69
Statement: 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.

RFQX-CVS124-0344

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 69
Statement: SUV2_INFO 114 in CVS123 prevents the scenario of erasing the copied bootloader while boot loader update and leaving the ECU without any bootloader.

RFQX-CVS124-0349

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 70
Statement: 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.

RFQX-CVS124-0351

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 71
Statement: 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.

RFQX-CVS124-0353

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 71
Statement: in CVS123.

RFQX-CVS124-0355

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 71
Statement: 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-0xFF

RFQX-CVS124-0357

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 72
Statement: 5.6.2.5 Message flow example(s) RoutineControl (EraseMemory) Example #1: Request: client → server

RFQX-CVS124-0358

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 72
Statement: This is an example where the client requests to erase a module in the server memory by a given memoryStartAddress and memorySize.

RFQX-CVS124-0359

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 73
Statement: This example reports a failure when the erase operation is started, e.g. memory failure.

RFQX-CVS124-0360

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 73
Statement: This is an example where the client requests to erase a module with module index 3 in the server’s memory.

RFQX-CVS124-0361

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 74
Statement: The RoutineIdentifier may verify the authenticity of the received file package. See CVS123 and

RFQX-CVS124-0363

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 74
Statement: The authenticity verification performed by the RoutineIdentifier 0x2401 Software Installation does not exempt the authenticity verification for RoutineIdentifier 0xFF01 – CheckProgrammingDependencies.

RFQX-CVS124-0378

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 76
Statement: Implementation hint can be seen on Annex B.

RFQX-CVS124-0394

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 79
Statement: This is an example where the client requests CheckProgrammingDependencies to finalize the validation after software download.

RFQX-CVS124-0395

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 79
Statement: The checksum was contained in the data stream programmed to the memory.

RFQX-CVS124-0396

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 79
Statement: 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.

RFQX-CVS124-0399

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 80
Statement: 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 M

RFQX-CVS124-0401

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 80
Statement: The occurrence counter is used in DTCExtDataRecords, see section 5.5.10.2.8.

RFQX-CVS124-0411

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 81
Statement: The timestamp of occurrence is used at DTCExtDataRecords, see section 5.5.10.2.8.

RFQX-CVS124-0413

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 81
Statement: The timestamp is presented in SAE J1939-71 format without local hour/minute offsets.

RFQX-CVS124-0414

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 81
Statement: 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 timestamps

RFQX-CVS124-0419

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 82
Statement: The total vehicle distance at occurrence is used in DTCExtDataRecords, see section 5.5.10.2.8.

RFQX-CVS124-0422

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 82
Statement: The latest distance value is updated at a change of DTC status bits 0 (testFailed) and 3

RFQX-CVS124-0423

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 82
Statement: 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.

RFQX-CVS124-0424

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 82
Statement: The first distance value is updated at the first change of DTC status bits 0 (testFailed) and 3

RFQX-CVS124-0425

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 83
Statement: The operational hours at occurrence is used at DTCExtDataRecords, see section 5.5.10.2.8.

RFQX-CVS124-0426

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 83
Statement: The operational hours are presented by a four byte integer, big endian, with , half second per bit (0,5s/bit).

RFQX-CVS124-0428

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 83
Statement: The latest operational hours value is updated at a change of DTC status bits 0 (testFailed) and 3 (confirmedDTC) both from 0 to 1.

RFQX-CVS124-0429

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 83
Statement: 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.

RFQX-CVS124-0430

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 83
Statement: 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.

RFQX-CVS124-0440

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: F197 structure added

RFQX-CVS124-0441

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: F198 Request and response format

RFQX-CVS124-0442

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: F199 Request and response format

RFQX-CVS124-0443

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: F19A Request and response format

RFQX-CVS124-0444

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: NRC for RBACC check failures

RFQX-CVS124-0445

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: ,

RFQX-CVS124-0446

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: ,

RFQX-CVS124-0447

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: ,

RFQX-CVS124-0448

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: ,

RFQX-CVS124-0449

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: ,

RFQX-CVS124-0450

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: ,

RFQX-CVS124-0451

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 90
Statement: Requirements, Request and response formats for the ControlDTCSetting(0x85) added.

RFQX-CVS124-0452

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 90
Statement: Added semantic Identifier DIDs, changed the NodeUID DID to INTERNAL

RFQX-CVS124-0453

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: Change in the length of NodeUID(0xF1AF)

RFQX-CVS124-0454

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 90
Statement: Change in the retrieval method for NodeUID(0xF1AF)

RFQX-CVS124-0455

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 90
Statement: 0xF1B9 RBACCIdentifierNumber is changed to Mandatory

RFQX-CVS124-0456

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 90
Statement: 0xF1BA RBACCStructureVersion,bit-length changed

RFQX-CVS124-0457

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: Changes for service (0x84) and (0x31)

RFQX-CVS124-0458

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: Updated the document references

RFQX-CVS124-0459

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: 0XCAFE and 0xFF02 are updated to Mandatory

RFQX-CVS124-0460

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 90
Statement: Modifcations on the bit values and new bit added

RFQX-CVS124-0461

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 90
Statement: 0x05 is changed to Mandatory 6 Normative references: Updated the referenced documents and versions Removed Requirements and infos

RFQX-CVS124-0462

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: (0x86) service removed

RFQX-CVS124-0463

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: ,

RFQX-CVS124-0464

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 90
Statement: Removed the reserved DID ranges and 0xF1C1

RFQX-CVS124-0465

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 90
Statement: 0xF19E ODXFileDataIdentifier is removed 2024-10 First issue

RFQX-CVS151-0001

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 1
Statement: 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.

RFQX-CVS151-0005

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: 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.

RFQX-CVS151-0007

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: The RBAC logic is typically part of the ECU application- and boot-software.

RFQX-CVS151-0008

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: The RBACC is typically injected into the ECU during production, using a secure protocol.

RFQX-CVS151-0009

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: As previously mentioned, each ECU (supporting RBAC) will be programmed with an RBACC, RBAC Configuration, containing the rules to drive the RBAC logic.

RFQX-CVS151-0010

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: The RBACC contains one or several role-configurations (see Figure 2 for a visual representation).

RFQX-CVS151-0012

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 5
Statement: 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.

RFQX-CVS151-0013

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 5
Statement: A role-configuration, in its turn, contains one or many rules (see Figure 2 for a visual representation).

RFQX-CVS151-0015

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 5
Statement: Each rule can be of either DENY or ALLOW type.

RFQX-CVS151-0017

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 5
Statement: 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.

RFQX-CVS151-0021

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 5
Statement: 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.

RFQX-CVS151-0022

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: 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.

RFQX-CVS151-0024

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: 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.

RFQX-CVS151-0025

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: 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).

RFQX-CVS151-0026

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: 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.

RFQX-CVS151-0027

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: See Annex B for a more detailed example of RBACC.

RFQX-CVS151-0029

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: Allow rules defined in role 0 are an exception to this requirement, see 3.13.

RFQX-CVS151-0031

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 8
Statement: The version specifies the structure of RBACC.

RFQX-CVS151-0038

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 8
Statement: See RBACStructureVersion definition in CVS124.

RFQX-CVS151-0039

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 8
Statement: This field identifies the RBACC using 16 octets.

RFQX-CVS151-0042

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 8
Statement: See RBACIdentifierNumber definition in CVS124.

RFQX-CVS151-0043

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 8
Statement: A 32-bit unsigned integer that represents one role.

RFQX-CVS151-0046

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 9
Statement: The diagnostic pattern identifies the diagnostic request.

RFQX-CVS151-0047

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 9
Statement: This type of rule can be used to create rules for all types of diagnostic requests.

RFQX-CVS151-0052

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 9
Statement: 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.

RFQX-CVS151-0056

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 10
Statement: This type of rule can be used to create rules for all types of diagnostic requests that makes use of RIDs.

RFQX-CVS151-0059

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 11
Statement: 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).

RFQX-CVS151-0061

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 11
Statement: A snippet from https://datatracker.ietf.org/doc/html/rfc5280#section-4.1 that specifies the layout of a certificate extension.

RFQX-CVS151-0063

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 12
Statement: Inside the extnValue (see snipped above) is one instance of a RBACC (see 3.3).

RFQX-CVS151-0064

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 12
Statement: 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.

RFQX-CVS151-0067

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 12
Statement: Figure 3 shows the interaction between the diagnostics server and the RBAC enforcer logic.

RFQX-CVS151-0069

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: As previously stated and as show in Figure 4, deny rules takes precedence over allow rules.

RFQX-CVS151-0070

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: 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.

RFQX-CVS151-0072

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 16
Statement: The “request.conditions COMPLIES_WITH rule.settings” refers to evaluate if the request conditions fulfils the expected rule settings.

RFQX-CVS151-0076

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: In Figure 8, the RBAC complete rule evaluation logic is described.

RFQX-CVS151-0077

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 19
Statement: 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).

RFQX-CVS151-0090

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: 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.

RFQX-CVS154-0001

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 1
Statement: 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.

RFQX-CVS154-0005

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: See further chapter 3.2 DSC ASN.1 definition for element types.

RFQX-CVS154-0006

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: 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 structure

RFQX-CVS154-0007

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 5
Statement: • version: specifies a version of the DSC structure, namely the DSC ASN.1 definition and its elements within the DSC instance.

RFQX-CVS154-0019

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: The VerificationEntry is of ASN.1 type CHOICE, where the choice stipulates the verification strategy for a piece of data.

RFQX-CVS154-0020

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: See 3.2 for the context-specific tag number for the VerificationEntry choices.

RFQX-CVS154-0022

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: When the server is instructed to verify the programmed data, in general the following actions are taken by the server.

RFQX-CVS154-0023

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: However, the instance specification may state specialized actions: • Server processes each VerificationEntry one by one.

RFQX-CVS154-0024

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: Definition of hashCmp fields: Refer to Figure 3 for type definitions of each field.

RFQX-CVS154-0028

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 7
Statement: The encryptionEntry is of ASN.1 type CHOICE stipulating the decryption strategy for a piece of data.

RFQX-CVS154-0030

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 7
Statement: See 3.2 for the context-specific tag number for the EncryptionEntry choices.

RFQX-CVS154-0033

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 9
Statement: An ItemEntry is of ASN.1 type CHOICE, where the choice stipulates the type of item the ItemEntry holds.

RFQX-CVS31-0002

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 3
Statement: Foreword This CVS31 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable.

RFQX-CVS31-0011

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 7
Statement: 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.

RFQX-CVS31-0013

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 7
Statement: In this document, each subFunction (ISO 14229-1:2020) is described in its own sub-section.

RFQX-CVS31-0018

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 8
Statement: For details on Authentication delay timer, refer to chapter 4.8.

RFQX-CVS31-0023

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 9
Statement: For details in how to validate a client certificate, refer to chapter 4.1.

RFQX-CVS31-0032

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 11
Statement: 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). Additionally, the field proves that the same message sent by the client has been received by the server and vice-versa.

RFQX-CVS31-0034

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 11
Statement: 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.

RFQX-CVS31-0035

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 11
Statement: This field provides the client with the necessary server-side data for the chosen key-exchange scheme/algorithm.

RFQX-CVS31-0039

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 11
Statement: 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).

RFQX-CVS31-0044

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 12
Statement: For details on Authentication completion timer, refer to chapter 4.9.

RFQX-CVS31-0050

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 13
Statement: 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).

RFQX-CVS31-0052

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 13
Statement: The reason for the concatenation, is to ensure that the full communication (all sent and received requests and responses) has integrity.

RFQX-CVS31-0053

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 13
Statement: This field provides the server with the necessary client-side data for the chosen key-exchange scheme/algorithm.

RFQX-CVS31-0055

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: The sessionKeyInfo includes a signature that proves to the client that the server has accepted the proofOfOwnership (ISO 14229-1:2020).

RFQX-CVS31-0057

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: For obvious reasons, the sessionKeyInfo in the ProofOfOwnershipres is not included, in the “concatenation” (see pseudo code above) when the signature is being calculated.

RFQX-CVS31-0064

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: This chapter specifies the behaviour of the deAuthenticate subfunction.

RFQX-CVS31-0069

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: 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.

RFQX-CVS31-0072

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 16
Statement: 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.

RFQX-CVS31-0076

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 16
Statement: The signature algorithm in the client, server and authentication CA certificates are ED25519 (1.3.101.112).

RFQX-CVS31-0082

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: • Check if the NodeUID of the server is present in the NodeUIDs extension.

RFQX-CVS31-0085

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: A certificate without NodeUID extension implies that the certificate is applicable for any NodeUID.

RFQX-CVS31-0086

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: The maximum number of elements in the list (number of ids) is limited by the maximum size of the certificate.

RFQX-CVS31-0087

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 18
Statement: For the length of NodeUID see (CVS124).

RFQX-CVS31-0091

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: The D-RBACC extension defines client-specific rules that override the role-based access control configuration in the server.

RFQX-CVS31-0092

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: 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.

RFQX-CVS31-0097

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 19
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.

RFQX-CVS31-0107

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 19
Statement: The notBefore and notAfter are received as fields in the certificate while Certificate-Time is the EMP entity defined in CVS34.

RFQX-CVS31-0108

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: • The server is reset (i.e server is power cycled).

RFQX-CVS31-0109

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 20
Statement: State-keeping

RFQX-CVS31-0110

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 20
Statement: • Power failure.

RFQX-CVS31-0112

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: 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.

RFQX-CVS31-0114

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 20
Statement: • Power failure.

RFQX-CVS31-0115

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: • Successful deAuthenticate (see 3.3) subFunction (ISO 14229-1:2020).

RFQX-CVS31-0116

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: • A new successful authentication is established.

RFQX-CVS31-0117

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 20
Statement: • By passive de-authentication, see 4.7.

RFQX-CVS31-0118

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: Authentication state invalidated by the server implies that any unlocked services and sessionKey is locked/invalidated.

RFQX-CVS31-0121

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 20
Statement: • Authentication completion timer.

RFQX-CVS31-0122

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 20
Statement: • Client’s certificate public key

RFQX-CVS31-0123

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 21
Statement: • Client D-RBACC, if provided in the client’s certificate

RFQX-CVS31-0124

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 21
Statement: • Server ephemeral private key

RFQX-CVS31-0125

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 21
Statement: • H0 hash value

RFQX-CVS31-0126

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 21
Statement: The server ephemeral private key is the pair of the public key (ephemeralPublicKeyServer) sent as verifyCertificateBidirectional response.

RFQX-CVS31-0127

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 21
Statement: H0 hash value is calculated as part of proofOfOwnershipServer in verifyCertificateBidirectional response.

RFQX-CVS31-0129

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 21
Statement: • A3 Timer for passive de-authentication information.

RFQX-CVS31-0130

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 21
Statement: • Client address that issued the authentication request.

RFQX-CVS31-0131

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 21
Statement: • Client roles (ECU diagnostic Role extension in client’s certificate)

RFQX-CVS31-0132

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 21
Statement: • Client D-RBACC, if provided in the client’s certificate

RFQX-CVS31-0135

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 22
Statement: 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.

RFQX-CVS31-0136

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 22
Statement: An overview of the key-exchange process is shown in Figure 4.

RFQX-CVS31-0139

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 22
Statement: 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.

RFQX-CVS31-0140

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 22
Statement: The SessionKey is referred as SecuredDataTransmissionKey in (CVS32).

RFQX-CVS31-0144

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 23
Statement: 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).

RFQX-CVS31-0145

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 23
Statement: Two passive de-authentication mechanisms are described in (ISO 14229-1:2020).

RFQX-CVS31-0149

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 23
Statement: For this requirement, “same client” refers to a request that originates from the same tester address as the tester currently authenticated by the server.

RFQX-CVS31-0150

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 23
Statement: When a request is received, authenticated or not, the server upon verifying it is from the same client will restart the timer (A3).

RFQX-CVS31-0159

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 24
Statement: The Authentication completion timer represents the timeframe that the client is allowed to perform proofOfOwnership request after a verifyCertificateBidirectional request.

RFQX-CVS31-0161

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 24
Statement: The Authentication completion timer is started upon positive response for verifyCertificateBidirectional request.

RFQX-CVS31-0162

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Migrated Req. into

RFQX-CVS31-0163

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Added

RFQX-CVS31-0164

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
Statement: Removed AUTH_REQ 137 since it is covered by AUTH_REQ 135 Removed in Annex A the reference to verifyCertificatesUniDirectional since it is not supported

RFQX-CVS31-0166

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: to

RFQX-CVS31-0167

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Changed tag

RFQX-CVS31-0168

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: to

RFQX-CVS31-0169

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Changed tag

RFQX-CVS31-0170

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: to

RFQX-CVS31-0171

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Changed tag

RFQX-CVS31-0172

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: to

RFQX-CVS31-0173

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Changed tag

RFQX-CVS31-0174

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: to

RFQX-CVS31-0175

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Changed tag

RFQX-CVS31-0176

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: to

RFQX-CVS31-0177

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Changed tag

RFQX-CVS31-0178

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: to

RFQX-CVS31-0179

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Changed tag

RFQX-CVS31-0180

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: to

RFQX-CVS31-0181

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Changed tag

RFQX-CVS31-0182

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: to

RFQX-CVS31-0183

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Changed tag

RFQX-CVS31-0184

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: to

RFQX-CVS31-0185

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Duplicated AUTH_INFO due to typo.

RFQX-CVS31-0186

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: to

RFQX-CVS31-0187

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Changed tag

RFQX-CVS31-0188

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: to

RFQX-CVS31-0189

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Changed tag

RFQX-CVS31-0190

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: to

RFQX-CVS31-0191

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Changed tag

RFQX-CVS31-0192

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: to

RFQX-CVS31-0193

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Changed tag

RFQX-CVS31-0194

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: to

RFQX-CVS31-0195

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Changed tag

RFQX-CVS31-0196

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: to

RFQX-CVS31-0197

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
Statement: 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 into

RFQX-CVS31-0198

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Migrated Info into

RFQX-CVS31-0199

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Migrated Req.

RFQX-CVS31-0200

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Added

RFQX-CVS31-0201

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Added chapter for Certificate validity Added

RFQX-CVS31-0202

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Added

RFQX-CVS31-0203

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Added OID for client authentication Changed

RFQX-CVS31-0204

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Fixed typo Changed

RFQX-CVS31-0205

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (Removed “shown in only”) Changed

RFQX-CVS31-0206

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (VerifyCertificateres -> VerifyCertificates) Changed Table 5 (lengthofCertificateClient -> lengthOfCertificateClient) Changed Table 6 (lengthOfCertitifacteServer -> lengthOfCertificateServer) Changed

RFQX-CVS31-0207

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (fails -> failure) Changed

RFQX-CVS31-0208

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (fails -> failure) Changed Table 7 (EphemeralPublicKeyClient -> ephemeralPublicKeyClient) Removed ambiguity Changed

RFQX-CVS31-0209

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: Removed

RFQX-CVS31-0210

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: since it is covered by

RFQX-CVS31-0211

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
Statement: Removed in Annex A the reference to verifyCertificatesUniDirectional since it is not supported

RFQX-CVS31-0212

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0213

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0214

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0215

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0216

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0217

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0218

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0219

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0220

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0221

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0222

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Added

RFQX-CVS31-0223

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Added

RFQX-CVS31-0224

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Removed

RFQX-CVS31-0225

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Added

RFQX-CVS31-0226

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Added

RFQX-CVS31-0227

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Added

RFQX-CVS31-0228

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: and

RFQX-CVS31-0229

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
Statement: Updated document quirks chapter Removed the information that italic terms are often clickable.

RFQX-CVS31-0230

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
Statement: Reformulation for clarity improvement Changed

RFQX-CVS31-0231

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0232

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0233

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0234

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0235

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0236

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0237

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0238

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0239

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0240

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0241

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Changed

RFQX-CVS31-0242

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: 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) Changed

RFQX-CVS31-0243

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
Statement: (Changed POO -> proofOfOwnershipServer) Removed

RFQX-CVS31-0244

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
Statement: (Maximum size of elements is to be defined by max size of certificate) Added

RFQX-CVS31-0245

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
Statement: (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

RFQX-CVS31-0246

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
Statement: Added Chapter 2.1.1.2 lengthOfCertificateClient Added

RFQX-CVS31-0247

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Added

RFQX-CVS31-0248

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Added

RFQX-CVS31-0249

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
Statement: Clarified the signature algorithm to be used over the authentication process Removed

RFQX-CVS31-0250

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Added

RFQX-CVS31-0251

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Added

RFQX-CVS31-0252

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Added

RFQX-CVS31-0253

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 30
Statement: Added

RFQX-CVS31-0254

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 30
Statement: 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 subfunction

RFQX-CVS32-0002

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 2
Statement: Foreword This CVS32 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable.

RFQX-CVS32-0005

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: The 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]

RFQX-CVS32-0006

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 4
Statement: The 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.

RFQX-CVS32-0010

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: 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.

RFQX-CVS32-0011

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: Figure 1 shows the layout of an SDT message with its protocol elements (for details refer to ISO 14229-1:2020 [1]).

RFQX-CVS32-0013

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: ECUs with diagnostic servers in multiple execution states, e.g.

RFQX-CVS32-0015

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: A prerequisite for the SDT service is that a SecuredDataTransmissionKey has been established between client and server using the 0x29 service [6].

RFQX-CVS32-0017

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 6
Statement: (There may be more than one authentication state).

RFQX-CVS32-0018

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 7
Statement: 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].

RFQX-CVS32-0022

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 7
Statement: This specification defines two counters, one for the request messages and one for responses.

RFQX-CVS32-0023

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 7
Statement: The reason for the two separate counters is that the UDS standard allows for a request to result in multiple responses, e.g.

RFQX-CVS32-0024

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 7
Statement: 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).

RFQX-CVS32-0032

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 8
Statement: 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.

RFQX-CVS32-0034

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 8
Statement: The server handles the exhaustion of PREQARC and PRESARC with its “normal behavior”.

RFQX-CVS32-0035

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 8
Statement: ).

RFQX-CVS32-0036

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 8
Statement: ).

RFQX-CVS32-0037

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 8
Statement: The requirements above are illustrated in Figure 2.

RFQX-CVS32-0038

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 8
Statement: 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.

RFQX-CVS32-0039

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 9
Statement: 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. This TAG is used to guarantee request/response coherency and the corresponding state variable is called PREQTAG (Previous REQuest TAG).

RFQX-CVS32-0041

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 9
Statement: The requirements regarding PREQTAG are detailed in sections 3.2.2 and 3.2.3 since they differ slightly between CipherSchemes.

RFQX-CVS32-0042

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 9
Statement: Figure 3 illustrates transaction coherency and the use of PREQTAG.

RFQX-CVS32-0043

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 9
Statement: The authenticity, and optionally confidentiality, of an SDT message is provided by the CipherScheme with which the SDT message is authenticated/encrypted.

RFQX-CVS32-0045

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 10
Statement: The 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.

RFQX-CVS32-0049

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 10
Statement: The client may alter the CipherScheme between SDT requests within the same SDT sequence.

RFQX-CVS32-0050

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 10
Statement: Since the two CipherSchemes require different key material, the KDF has to be re-run if the CipherScheme changes.

RFQX-CVS32-0052

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 10
Statement: In the following, these state variables are called PSIGENCRYPT (Previous SIGENCRYPT) and PKEY (Previous KEY).

RFQX-CVS32-0055

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 11
Statement: Figure 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

RFQX-CVS32-0060

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 11
Statement: Example: “SDT_0x84_KEY” = 5344545F307838345F4B4559 (UTF-8 encoded hex) CipherScheme = 02 (SDT_AEAD_CHACHA20_POLY1305) ➔ info := 5344545F307838345F4B455902

RFQX-CVS32-0061

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 11
Statement: 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.

RFQX-CVS32-0062

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 12
Statement: okm is the output key material octet string of length L.

RFQX-CVS32-0063

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 12
Statement: This section describes a CipherScheme based on AEAD_CHACHA20_POLY1305 [9].

RFQX-CVS32-0067

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 12
Statement: The above requirements are visualized in Figure 5.

RFQX-CVS32-0072

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 12
Statement: The plaintext (𝑃) and ciphertext (𝐶) octet strings are of the same length and a concatenation of the INTMSGREQID and SRVSPECPARAM protocol elements.

RFQX-CVS32-0079

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 13
Statement: element of the response.

RFQX-CVS32-0081

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 13
Statement: element of the request.

RFQX-CVS32-0086

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: 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.

RFQX-CVS32-0087

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: The encircled “||” denotes concatenation and the concatenation order is top to bottom in the figure.

RFQX-CVS32-0089

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 14
Statement: Encrypted data in the figure is denoted “x..x”, one “x” denotes one encrypted octet.

RFQX-CVS32-0090

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: This 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.

RFQX-CVS32-0094

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: The above requirements are visualized in Figure 7.

RFQX-CVS32-0097

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: 𝑃: The 𝑃 (Plaintext) is a zero length octet string (null).

RFQX-CVS32-0098

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 15
Statement: 𝐶: The 𝐶 (Ciphertext) is a zero length octet string (null).

RFQX-CVS32-0105

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 16
Statement: element of the response.

RFQX-CVS32-0107

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 16
Statement: element of the request.

RFQX-CVS32-0112

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
Statement: 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.

RFQX-CVS32-0113

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 17
Statement: The encircled “||” denotes concatenation and the concatenation order is top to bottom relative the symbol.

RFQX-CVS32-0114

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: This 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.

RFQX-CVS32-0115

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: A UDS request/response, in the figure, means any request/response other than SDT (service 0x84).

RFQX-CVS32-0116

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: The SDT positive response may of course contain an encapsulated negative UDS response.

RFQX-CVS32-0117

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: Figure 10Figure 10 illustrates error- and state handling in the server’s security sub-layer.

RFQX-CVS32-0118

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 18
Statement: Note that the markings in the figure, (“S1” through “S3”), and the values for the state variables are correlated with Figure 3.

RFQX-CVS32-0127

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: For example, APAR dictates encryption, but SIGENCRYPT does not offer encryption.

RFQX-CVS32-0129

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: For example, the CipherScheme indicated by SIGENCRYPT produces a TAG of a length different from that indicated by SIGLEN.

RFQX-CVS32-0132

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: This means that if the server generates an SDT negative response, the server’s state remains unchanged, i.e.

RFQX-CVS32-0134

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: This means that if the server fails to generate an SDT response, the server’s state remains unchanged, i.e.

RFQX-CVS32-0135

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 20
Statement: As mentioned above in this specification, the UDS standard allows for a request to result in multiple responses, e.g.

RFQX-CVS32-0136

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 21
Statement: 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.

RFQX-CVS32-0137

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 21
Statement: 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.

RFQX-CVS32-0138

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 21
Statement: Figure 12Figure 12 illustrates error- and state handling in the client’s security sub-layer.

RFQX-CVS32-0148

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 23
Statement: This means that if the client fails to verify/decrypt the SDT response, the client’s state remains unchanged, i.e.

RFQX-CVS32-0149

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 23
Statement: Messages can get lost going from client to server, or vice versa.

RFQX-CVS32-0150

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 23
Statement: Note that busyRepeatRequest, NRC 0x21 (BRR), can be sent in an SDT negative response, or, encapsulated in an SDT positive response.

RFQX-CVS32-0152

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 23
Statement: .

RFQX-CVS32-0153

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 23
Statement: A negative UDS response BRR encapsulated in a positive SDT response can of course never result in the resending of an old SDT request.

RFQX-CVS32-0154

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: Updated

RFQX-CVS32-0155

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: Updated

RFQX-CVS32-0156

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: Updated

RFQX-CVS32-0157

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: Updated

RFQX-CVS32-0158

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: Updated

RFQX-CVS32-0159

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: Updated

RFQX-CVS32-0160

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: Updated

RFQX-CVS32-0161

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: Updated

RFQX-CVS32-0162

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: Updated

RFQX-CVS32-0163

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: Updated

RFQX-CVS32-0164

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: Updated

RFQX-CVS32-0165

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 28
Statement: SDT_AES_SIV_CMAC_256 and SDT_CMAC_128 was deprecated and replaced with SDT_AEAD_CHACHA20_POLY1305 and SDT_POLY1305.

RFQX-CVS32-0166

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: (new cipher-schemes) Updated Table 2 (new cipher-schemes) Updated

RFQX-CVS32-0167

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0168

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0169

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 28
Statement: (new cipher-schemes) Updated Figure 4 (new cipher-schemes) Updated

RFQX-CVS32-0170

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 28
Statement: (new cipher-schemes) Updated 3.2.2 heading (new cipher-schemes) Updated

RFQX-CVS32-0171

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 28
Statement: (new cipher-schemes) Updated Figure 5 annotation (new cipher-schemes) Updated

RFQX-CVS32-0172

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0173

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0174

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0175

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0176

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0177

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0178

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0179

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0180

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 28
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0181

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 28
Statement: (new cipher-schemes) Updated Figure 6 (new cipher-schemes)

RFQX-CVS32-0182

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0183

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0184

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0185

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0186

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Added

RFQX-CVS32-0187

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
Statement: (new cipher-schemes) Added Figure 7 (new cipher-schemes) Updated

RFQX-CVS32-0188

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Added

RFQX-CVS32-0189

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Added

RFQX-CVS32-0190

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Added

RFQX-CVS32-0191

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0192

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0193

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0194

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0195

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0196

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0197

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0198

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0199

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0200

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
Statement: (new cipher-schemes) Updated Figure 8 (new cipher-schemes) Updated

RFQX-CVS32-0201

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: source document page 29
Statement: (new cipher-schemes) Updated

RFQX-CVS32-0202

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
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.

RFQX-CVS32-0203

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: source document page 29
Statement: and updated Figure 9.) 2025-08 1 This standard has been revised and is valid for continued use.

Customer Readiness Summary

Recommendation

Current Gate

Top 5 Customer Clarification Questions

Known Limitations

Customer Clarification Questions

Product/System Boundary

CQ-BOUNDARY-03

CQ-BOUNDARY-05

CQ-BOUNDARY-127

CQ-BOUNDARY-158

CQ-BOUNDARY-199

CQ-BOUNDARY-201

CQ-BOUNDARY-01

CQ-BOUNDARY-02

CQ-BOUNDARY-04

CQ-BOUNDARY-06

CQ-BOUNDARY-07

CQ-BOUNDARY-08

CQ-BOUNDARY-09

CQ-BOUNDARY-10

CQ-BOUNDARY-100

CQ-BOUNDARY-101

CQ-BOUNDARY-102

CQ-BOUNDARY-103

CQ-BOUNDARY-104

CQ-BOUNDARY-105

CQ-BOUNDARY-106

CQ-BOUNDARY-107

CQ-BOUNDARY-108

CQ-BOUNDARY-109

CQ-BOUNDARY-11

CQ-BOUNDARY-110

CQ-BOUNDARY-111

CQ-BOUNDARY-112

CQ-BOUNDARY-113

CQ-BOUNDARY-114

CQ-BOUNDARY-115

CQ-BOUNDARY-116

CQ-BOUNDARY-117

CQ-BOUNDARY-118

CQ-BOUNDARY-119

CQ-BOUNDARY-12

CQ-BOUNDARY-120

CQ-BOUNDARY-121

CQ-BOUNDARY-122

CQ-BOUNDARY-123

CQ-BOUNDARY-124

CQ-BOUNDARY-125

CQ-BOUNDARY-126

CQ-BOUNDARY-128

CQ-BOUNDARY-129

CQ-BOUNDARY-13

CQ-BOUNDARY-130

CQ-BOUNDARY-131

CQ-BOUNDARY-132

CQ-BOUNDARY-133

CQ-BOUNDARY-134

CQ-BOUNDARY-135

CQ-BOUNDARY-136

CQ-BOUNDARY-137

CQ-BOUNDARY-138

CQ-BOUNDARY-139

CQ-BOUNDARY-14

CQ-BOUNDARY-140

CQ-BOUNDARY-141

CQ-BOUNDARY-142

CQ-BOUNDARY-143

CQ-BOUNDARY-144

CQ-BOUNDARY-145

CQ-BOUNDARY-146

CQ-BOUNDARY-147

CQ-BOUNDARY-148

CQ-BOUNDARY-149

CQ-BOUNDARY-15

CQ-BOUNDARY-150

CQ-BOUNDARY-151

CQ-BOUNDARY-152

CQ-BOUNDARY-153