Customer Question Pack

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

Remaining Questions

CQ-BOUNDARY-03

Priority: P1
Status: Not Applicable
Source of question: source document page 3
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-1001379436-P10-000-01-0003
Source document / section / page: source document page 3
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-05

Priority: P1
Status: Not Applicable
Source of question: source document page 5
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-1001379436-P10-000-01-0011
Source document / section / page: source document page 5
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-127

Priority: P1
Status: Not Applicable
Source of question: source document page 6
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0005
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-158

Priority: P1
Status: Not Applicable
Source of question: source document page 52
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0246
Source document / section / page: source document page 52
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-199

Priority: P1
Status: Not Applicable
Source of question: source document page 9
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS154-0035
Source document / section / page: source document page 9
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-201

Priority: P1
Status: Not Applicable
Source of question: source document page 4
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0006
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-02

Priority: P2
Status: Not Applicable
Source of question: source document page 10
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Blocks implementation planning
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS123-2-0055
Source document / section / page: source document page 10
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-01

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 3
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-1001379436-P10-000-01-0001
Source document / section / page: source document page 3
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-02

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 3
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-1001379436-P10-000-01-0002
Source document / section / page: source document page 3
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-04

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 5
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-1001379436-P10-000-01-0006
Source document / section / page: source document page 5
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-06

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 6
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-1001379436-P10-000-01-0020
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-07

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 7
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-1001379436-P10-000-01-0023
Source document / section / page: source document page 7
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-08

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0003
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-09

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 12
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0046
Source document / section / page: source document page 12
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-10

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 12
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0048
Source document / section / page: source document page 12
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-100

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 19
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0146
Source document / section / page: source document page 19
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-101

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 19
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0147
Source document / section / page: source document page 19
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-102

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 19
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0149
Source document / section / page: source document page 19
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-103

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0150
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-104

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0151
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-105

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0155
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-106

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0156
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-107

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0158
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-108

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0160
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-109

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0162
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-11

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 25
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0127
Source document / section / page: source document page 25
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-110

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 21
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0174
Source document / section / page: source document page 21
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-111

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 21
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0180
Source document / section / page: source document page 21
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-112

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 22
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0191
Source document / section / page: source document page 22
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-113

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 25
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0210
Source document / section / page: source document page 25
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-114

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 31
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0249
Source document / section / page: source document page 31
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-115

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 32
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0253
Source document / section / page: source document page 32
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-116

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 32
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0255
Source document / section / page: source document page 32
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-117

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 32
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0259
Source document / section / page: source document page 32
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-118

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 34
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0264
Source document / section / page: source document page 34
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-119

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 35
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0272
Source document / section / page: source document page 35
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-12

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 25
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0130
Source document / section / page: source document page 25
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-120

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 36
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0283
Source document / section / page: source document page 36
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-121

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 37
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0291
Source document / section / page: source document page 37
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-122

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 41
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0324
Source document / section / page: source document page 41
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-123

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 41
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0327
Source document / section / page: source document page 41
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-124

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 42
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0344
Source document / section / page: source document page 42
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-125

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 42
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0345
Source document / section / page: source document page 42
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-126

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 2
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0002
Source document / section / page: source document page 2
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-128

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 6
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0010
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-129

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 9
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0021
Source document / section / page: source document page 9
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-13

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 27
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0141
Source document / section / page: source document page 27
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-130

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 12
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0033
Source document / section / page: source document page 12
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-131

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0041
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-132

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0062
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-133

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 22
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0066
Source document / section / page: source document page 22
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-134

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 22
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0067
Source document / section / page: source document page 22
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-135

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 23
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0076
Source document / section / page: source document page 23
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-136

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 25
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0085
Source document / section / page: source document page 25
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-137

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 28
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0098
Source document / section / page: source document page 28
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-138

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0105
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-139

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0109
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-14

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0157
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-140

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0111
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-141

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0115
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-142

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0118
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-143

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0119
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-144

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0120
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-145

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0121
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-146

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0122
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-147

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0123
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-148

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0124
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-149

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0125
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-15

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 29
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0158
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-150

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0126
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-151

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0127
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-152

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 32
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0143
Source document / section / page: source document page 32
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-153

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 33
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0151
Source document / section / page: source document page 33
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-154

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 35
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0173
Source document / section / page: source document page 35
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-155

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 37
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0181
Source document / section / page: source document page 37
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-156

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 42
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0221
Source document / section / page: source document page 42
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-157

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 49
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0240
Source document / section / page: source document page 49
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-159

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 63
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0299
Source document / section / page: source document page 63
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-16

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 38
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0197
Source document / section / page: source document page 38
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-160

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 66
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0326
Source document / section / page: source document page 66
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-161

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 69
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0344
Source document / section / page: source document page 69
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-162

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 74
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0361
Source document / section / page: source document page 74
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-163

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 82
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS124-0419
Source document / section / page: source document page 82
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-164

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 1
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0001
Source document / section / page: source document page 1
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-165

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0005
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-166

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0007
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-167

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0008
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-168

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0009
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-169

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0010
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-17

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 41
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0222
Source document / section / page: source document page 41
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-170

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 5
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0012
Source document / section / page: source document page 5
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-171

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 5
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0013
Source document / section / page: source document page 5
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-172

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 5
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0021
Source document / section / page: source document page 5
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-173

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 6
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0022
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-174

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 6
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0025
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-175

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 6
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0027
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-176

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 6
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0029
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-177

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 8
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0031
Source document / section / page: source document page 8
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-178

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 8
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0038
Source document / section / page: source document page 8
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-179

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 8
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0039
Source document / section / page: source document page 8
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-18

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 43
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0223
Source document / section / page: source document page 43
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-180

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 8
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0042
Source document / section / page: source document page 8
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-181

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 8
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0043
Source document / section / page: source document page 8
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-182

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 9
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0046
Source document / section / page: source document page 9
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-183

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 9
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0047
Source document / section / page: source document page 9
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-184

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 9
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0052
Source document / section / page: source document page 9
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-185

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 10
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0056
Source document / section / page: source document page 10
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-186

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 11
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0059
Source document / section / page: source document page 11
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-187

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 11
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0061
Source document / section / page: source document page 11
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-188

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 12
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0063
Source document / section / page: source document page 12
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-189

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0069
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-19

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 43
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0229
Source document / section / page: source document page 43
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-190

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0070
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-191

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 16
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0072
Source document / section / page: source document page 16
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-192

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS151-0090
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-193

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 1
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS154-0001
Source document / section / page: source document page 1
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-194

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS154-0005
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-195

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 5
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS154-0007
Source document / section / page: source document page 5
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-196

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 7
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS154-0028
Source document / section / page: source document page 7
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-197

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 7
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS154-0030
Source document / section / page: source document page 7
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-198

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 9
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS154-0033
Source document / section / page: source document page 9
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-20

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 43
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0234
Source document / section / page: source document page 43
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-200

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 3
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0002
Source document / section / page: source document page 3
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-202

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 7
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0013
Source document / section / page: source document page 7
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-203

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 9
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0023
Source document / section / page: source document page 9
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-204

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 11
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0032
Source document / section / page: source document page 11
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-205

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 11
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0035
Source document / section / page: source document page 11
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-206

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 11
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0039
Source document / section / page: source document page 11
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-207

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 13
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0050
Source document / section / page: source document page 13
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-208

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 13
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0052
Source document / section / page: source document page 13
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-209

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 13
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0053
Source document / section / page: source document page 13
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-21

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 43
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0235
Source document / section / page: source document page 43
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-210

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0064
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-211

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0085
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-212

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0086
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-213

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 18
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0092
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-214

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 19
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0107
Source document / section / page: source document page 19
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-215

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0112
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-216

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0115
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-217

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 21
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0123
Source document / section / page: source document page 21
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-218

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 21
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0126
Source document / section / page: source document page 21
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-219

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 21
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0131
Source document / section / page: source document page 21
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-22

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 43
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0238
Source document / section / page: source document page 43
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-220

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 21
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0132
Source document / section / page: source document page 21
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-221

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 22
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0135
Source document / section / page: source document page 22
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-222

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 22
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0136
Source document / section / page: source document page 22
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-223

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 22
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0139
Source document / section / page: source document page 22
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-224

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 22
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0140
Source document / section / page: source document page 22
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-225

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0229
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-226

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0230
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-227

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0244
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-228

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0245
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-229

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS31-0254
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-23

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 43
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0240
Source document / section / page: source document page 43
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-230

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 2
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS32-0002
Source document / section / page: source document page 2
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-231

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS32-0005
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-232

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS32-0006
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-233

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 6
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS32-0013
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-234

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 6
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS32-0015
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-235

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 10
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS32-0045
Source document / section / page: source document page 10
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-236

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 10
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS32-0049
Source document / section / page: source document page 10
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-237

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 10
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS32-0050
Source document / section / page: source document page 10
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-238

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 10
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS32-0052
Source document / section / page: source document page 10
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-239

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 12
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS32-0062
Source document / section / page: source document page 12
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-24

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 43
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0241
Source document / section / page: source document page 43
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-240

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS32-0086
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-241

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS32-0112
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-242

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS32-0114
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-243

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS32-0117
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-244

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 21
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS32-0138
Source document / section / page: source document page 21
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-25

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 43
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0242
Source document / section / page: source document page 43
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-26

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 44
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0246
Source document / section / page: source document page 44
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-27

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 44
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0247
Source document / section / page: source document page 44
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-28

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 44
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0248
Source document / section / page: source document page 44
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-29

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 44
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0250
Source document / section / page: source document page 44
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-30

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 44
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0251
Source document / section / page: source document page 44
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-31

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 47
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0257
Source document / section / page: source document page 47
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-32

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 47
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0266
Source document / section / page: source document page 47
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-33

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 47
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0267
Source document / section / page: source document page 47
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-34

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 47
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0268
Source document / section / page: source document page 47
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-35

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 47
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0269
Source document / section / page: source document page 47
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-36

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 47
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0270
Source document / section / page: source document page 47
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-37

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 47
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0271
Source document / section / page: source document page 47
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-38

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 47
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0272
Source document / section / page: source document page 47
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-39

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 47
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0273
Source document / section / page: source document page 47
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-40

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 47
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0274
Source document / section / page: source document page 47
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-41

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 47
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0275
Source document / section / page: source document page 47
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-42

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 47
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0276
Source document / section / page: source document page 47
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-43

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 47
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0277
Source document / section / page: source document page 47
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-44

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 47
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0278
Source document / section / page: source document page 47
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-45

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 50
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0284
Source document / section / page: source document page 50
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-46

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 52
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0301
Source document / section / page: source document page 52
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-47

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 61
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-3299216-1-0309
Source document / section / page: source document page 61
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-48

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 1
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0001
Source document / section / page: source document page 1
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-49

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0005
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-50

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0006
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-51

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0007
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-52

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0009
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-53

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0012
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-54

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 5
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0015
Source document / section / page: source document page 5
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-55

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 5
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0016
Source document / section / page: source document page 5
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-56

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 5
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0017
Source document / section / page: source document page 5
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-57

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 6
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0025
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-58

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 6
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0027
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-59

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 8
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0033
Source document / section / page: source document page 8
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-60

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 9
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0045
Source document / section / page: source document page 9
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-61

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 10
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0054
Source document / section / page: source document page 10
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-62

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 11
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0060
Source document / section / page: source document page 11
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-63

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 11
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0063
Source document / section / page: source document page 11
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-64

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 12
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0073
Source document / section / page: source document page 12
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-65

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 12
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0074
Source document / section / page: source document page 12
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-66

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 12
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0080
Source document / section / page: source document page 12
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-67

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 13
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0081
Source document / section / page: source document page 13
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-68

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0082
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-69

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0084
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-70

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0086
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-71

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0087
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-72

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0089
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-73

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0090
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-74

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0091
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-75

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0096
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-76

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0098
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-77

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0099
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-78

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0100
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-79

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0101
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-80

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0102
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-81

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0103
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-82

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0104
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-83

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0106
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-84

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0107
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-85

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0108
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-86

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 16
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0111
Source document / section / page: source document page 16
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-87

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 16
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0113
Source document / section / page: source document page 16
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-88

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0115
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-89

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0116
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-90

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0117
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-91

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0118
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-92

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0122
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-93

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0129
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-94

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0130
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-95

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0131
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-96

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0132
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-97

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0133
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-98

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0139
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-99

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirements: RFQX-CVS123-2-0143
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-01

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-3299216-1-0005
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-02

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-3299216-1-0006
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-03

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 9
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-3299216-1-0023
Source document / section / page: source document page 9
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-04

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 13
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-3299216-1-0053
Source document / section / page: source document page 13
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-05

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-3299216-1-0080
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-06

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 34
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-3299216-1-0173
Source document / section / page: source document page 34
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-07

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS123-2-0008
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-08

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS123-2-0085
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-09

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 35
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS123-2-0280
Source document / section / page: source document page 35
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-10

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 37
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS123-2-0293
Source document / section / page: source document page 37
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-11

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 42
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS123-2-0346
Source document / section / page: source document page 42
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-12

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 28
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS124-0102
Source document / section / page: source document page 28
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-13

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 38
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS124-0194
Source document / section / page: source document page 38
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-14

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 63
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS124-0301
Source document / section / page: source document page 63
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-15

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 72
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS124-0357
Source document / section / page: source document page 72
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-16

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 5
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS151-0015
Source document / section / page: source document page 5
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-17

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 12
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS151-0064
Source document / section / page: source document page 12
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-18

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS31-0069
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-19

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 16
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS31-0072
Source document / section / page: source document page 16
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-20

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 6
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0010
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-21

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 6
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0011
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-22

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 7
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0018
Source document / section / page: source document page 7
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-23

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 7
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0022
Source document / section / page: source document page 7
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-24

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 7
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0023
Source document / section / page: source document page 7
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-25

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 7
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0024
Source document / section / page: source document page 7
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-26

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 8
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0032
Source document / section / page: source document page 8
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-27

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 8
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0034
Source document / section / page: source document page 8
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-28

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 8
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0037
Source document / section / page: source document page 8
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-29

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 8
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0038
Source document / section / page: source document page 8
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-30

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 9
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0039
Source document / section / page: source document page 9
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-31

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 9
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0041
Source document / section / page: source document page 9
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-32

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 9
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0042
Source document / section / page: source document page 9
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-33

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 9
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0043
Source document / section / page: source document page 9
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-34

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 11
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0055
Source document / section / page: source document page 11
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-35

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 11
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0060
Source document / section / page: source document page 11
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-36

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 11
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0061
Source document / section / page: source document page 11
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-37

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 12
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0063
Source document / section / page: source document page 12
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-38

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 12
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0067
Source document / section / page: source document page 12
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-39

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 12
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0072
Source document / section / page: source document page 12
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-40

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0087
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-41

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0089
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-42

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0090
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-43

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0094
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-44

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0097
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-45

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0098
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-46

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0113
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-47

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0115
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-48

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 18
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0116
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-49

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0118
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-50

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0127
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-51

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0129
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-52

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0132
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-53

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0134
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-54

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0135
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-55

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 21
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0136
Source document / section / page: source document page 21
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-56

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 21
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0137
Source document / section / page: source document page 21
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-57

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 23
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0148
Source document / section / page: source document page 23
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-58

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 23
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0149
Source document / section / page: source document page 23
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-59

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 23
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0150
Source document / section / page: source document page 23
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-60

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 23
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0153
Source document / section / page: source document page 23
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-61

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 28
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0165
Source document / section / page: source document page 28
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-62

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 28
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0169
Source document / section / page: source document page 28
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-63

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 28
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0170
Source document / section / page: source document page 28
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-64

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 28
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0171
Source document / section / page: source document page 28
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-65

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 28
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0181
Source document / section / page: source document page 28
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-66

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0187
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-67

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0200
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-68

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0202
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-69

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirements: RFQX-CVS32-0203
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-HSM-01

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 28
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.
Why it matters: Some security mechanisms require hardware-backed protection.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Software-only assumptions may be unsafe for key protection and platform integrity.
Related requirements: RFQX-3299216-1-0147
Source document / section / page: source document page 28
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-HSM-02

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Some security mechanisms require hardware-backed protection.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Software-only assumptions may be unsafe for key protection and platform integrity.
Related requirements: RFQX-CVS123-2-0127
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-HSM-03

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 19
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.
Why it matters: Some security mechanisms require hardware-backed protection.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Software-only assumptions may be unsafe for key protection and platform integrity.
Related requirements: RFQX-CVS123-2-0145
Source document / section / page: source document page 19
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-HSM-04

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 24
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.
Why it matters: Some security mechanisms require hardware-backed protection.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Software-only assumptions may be unsafe for key protection and platform integrity.
Related requirements: RFQX-CVS123-2-0202
Source document / section / page: source document page 24
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-HSM-05

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 32
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.
Why it matters: Some security mechanisms require hardware-backed protection.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Software-only assumptions may be unsafe for key protection and platform integrity.
Related requirements: RFQX-CVS123-2-0257
Source document / section / page: source document page 32
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-HSM-06

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 40
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.
Why it matters: Some security mechanisms require hardware-backed protection.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Software-only assumptions may be unsafe for key protection and platform integrity.
Related requirements: RFQX-CVS123-2-0315
Source document / section / page: source document page 40
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-HSM-07

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 41
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.
Why it matters: Some security mechanisms require hardware-backed protection.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Software-only assumptions may be unsafe for key protection and platform integrity.
Related requirements: RFQX-CVS123-2-0332
Source document / section / page: source document page 41
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-HSM-08

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 47
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.
Why it matters: Some security mechanisms require hardware-backed protection.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Software-only assumptions may be unsafe for key protection and platform integrity.
Related requirements: RFQX-CVS123-2-0348
Source document / section / page: source document page 47
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-LOG-01

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Logging and monitoring are evidence and response enablers.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Security events may be unavailable or unusable during incident response.
Related requirements: RFQX-CVS151-0076
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-01

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 4
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS123-2-0013
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-02

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 6
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS123-2-0026
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-03

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS123-2-0088
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-04

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS123-2-0092
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-05

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS123-2-0097
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-06

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 15
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS123-2-0105
Source document / section / page: source document page 15
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-07

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS123-2-0123
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-08

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS123-2-0124
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-09

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS123-2-0126
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-10

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS123-2-0128
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-11

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS123-2-0136
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-12

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS123-2-0159
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-13

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 28
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS123-2-0231
Source document / section / page: source document page 28
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-14

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 37
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS123-2-0290
Source document / section / page: source document page 37
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-15

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 9
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0022
Source document / section / page: source document page 9
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-16

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 11
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0026
Source document / section / page: source document page 11
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-17

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 13
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0035
Source document / section / page: source document page 13
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-18

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 16
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0047
Source document / section / page: source document page 16
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-19

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0052
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-20

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 27
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0090
Source document / section / page: source document page 27
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-21

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 27
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0091
Source document / section / page: source document page 27
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-22

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 28
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0095
Source document / section / page: source document page 28
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-23

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 28
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0096
Source document / section / page: source document page 28
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-24

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 28
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0097
Source document / section / page: source document page 28
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-25

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 28
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0099
Source document / section / page: source document page 28
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-26

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 28
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0100
Source document / section / page: source document page 28
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-27

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 28
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0101
Source document / section / page: source document page 28
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-28

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0103
Source document / section / page: source document page 28
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-29

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0106
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-30

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0107
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-31

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 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 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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0108
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-32

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0110
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-33

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0112
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-34

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0113
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-35

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 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 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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0114
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-36

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0116
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-37

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 32
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0136
Source document / section / page: source document page 32
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-38

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 35
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0170
Source document / section / page: source document page 35
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-39

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 37
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0188
Source document / section / page: source document page 37
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-40

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 38
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0189
Source document / section / page: source document page 38
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-41

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 38
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0190
Source document / section / page: source document page 38
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-42

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 38
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0191
Source document / section / page: source document page 38
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-43

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 39
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0200
Source document / section / page: source document page 39
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-44

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 40
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0208
Source document / section / page: source document page 40
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-45

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 40
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0211
Source document / section / page: source document page 40
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-46

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 41
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0214
Source document / section / page: source document page 41
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-47

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 41
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0218
Source document / section / page: source document page 41
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-48

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 43
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0231
Source document / section / page: source document page 43
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-49

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 55
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0261
Source document / section / page: source document page 55
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-50

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 55
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0262
Source document / section / page: source document page 55
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-51

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 57
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0271
Source document / section / page: source document page 57
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-52

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 61
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0286
Source document / section / page: source document page 61
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-53

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 62
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0293
Source document / section / page: source document page 62
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-54

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 69
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0342
Source document / section / page: source document page 69
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-55

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 72
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0358
Source document / section / page: source document page 72
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-56

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 73
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0359
Source document / section / page: source document page 73
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-57

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 73
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0360
Source document / section / page: source document page 73
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-58

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 74
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0363
Source document / section / page: source document page 74
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-59

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 79
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0394
Source document / section / page: source document page 79
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-60

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 79
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0395
Source document / section / page: source document page 79
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-61

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 80
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0401
Source document / section / page: source document page 80
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-62

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 81
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0411
Source document / section / page: source document page 81
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-63

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 81
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0413
Source document / section / page: source document page 81
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-64

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 82
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0422
Source document / section / page: source document page 82
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-65

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 82
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0423
Source document / section / page: source document page 82
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-66

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 82
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0424
Source document / section / page: source document page 82
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-67

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 83
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0425
Source document / section / page: source document page 83
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-68

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 83
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0426
Source document / section / page: source document page 83
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-69

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 83
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0428
Source document / section / page: source document page 83
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-70

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 83
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0429
Source document / section / page: source document page 83
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-71

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 83
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0430
Source document / section / page: source document page 83
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-72

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 90
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0451
Source document / section / page: source document page 90
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-73

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 90
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0452
Source document / section / page: source document page 90
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-74

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 90
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0454
Source document / section / page: source document page 90
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-75

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 90
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0455
Source document / section / page: source document page 90
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-76

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 90
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0456
Source document / section / page: source document page 90
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-77

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 90
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0460
Source document / section / page: source document page 90
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-78

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 90
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0461
Source document / section / page: source document page 90
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-79

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 90
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS124-0465
Source document / section / page: source document page 90
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-80

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 12
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS151-0067
Source document / section / page: source document page 12
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-81

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 19
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS151-0077
Source document / section / page: source document page 19
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-82

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 8
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS31-0018
Source document / section / page: source document page 8
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-83

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 12
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS31-0044
Source document / section / page: source document page 12
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-84

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 16
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS31-0076
Source document / section / page: source document page 16
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-85

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS31-0116
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-86

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS31-0118
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-87

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 21
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS31-0129
Source document / section / page: source document page 21
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-88

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 21
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS31-0130
Source document / section / page: source document page 21
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-89

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 23
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS31-0144
Source document / section / page: source document page 23
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-90

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 23
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS31-0145
Source document / section / page: source document page 23
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-91

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 24
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS31-0159
Source document / section / page: source document page 24
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-92

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 24
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS31-0161
Source document / section / page: source document page 24
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-93

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS31-0249
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-94

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 6
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.
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirements: RFQX-CVS32-0017
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-PKI-01

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 37
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.
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related requirements: RFQX-CVS123-2-0296
Source document / section / page: source document page 37
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-PKI-02

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 11
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.
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related requirements: RFQX-CVS31-0034
Source document / section / page: source document page 11
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-PKI-03

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related requirements: RFQX-CVS31-0055
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-PKI-04

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related requirements: RFQX-CVS31-0057
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-PKI-05

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 21
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.
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related requirements: RFQX-CVS31-0127
Source document / section / page: source document page 21
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-PKI-06

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related requirements: RFQX-CVS31-0164
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-PKI-07

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related requirements: RFQX-CVS31-0197
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-PKI-08

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related requirements: RFQX-CVS31-0211
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-PKI-09

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Identity and cryptography depend on correct trust-material lifecycle design.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Mis-owned certificates or keys can break diagnostics, update, and secure communication.
Related requirements: RFQX-CVS31-0246
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-UPDATE-01

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related requirements: RFQX-CVS123-2-0004
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-UPDATE-02

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 12
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.
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related requirements: RFQX-CVS123-2-0076
Source document / section / page: source document page 12
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-UPDATE-03

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 12
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.
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related requirements: RFQX-CVS123-2-0077
Source document / section / page: source document page 12
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-UPDATE-04

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related requirements: RFQX-CVS123-2-0083
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-UPDATE-05

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 14
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.
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related requirements: RFQX-CVS123-2-0095
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-UPDATE-06

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 16
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.
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related requirements: RFQX-CVS123-2-0109
Source document / section / page: source document page 16
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-UPDATE-07

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related requirements: RFQX-CVS123-2-0119
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-UPDATE-08

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related requirements: RFQX-CVS123-2-0120
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-UPDATE-09

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related requirements: RFQX-CVS123-2-0121
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-UPDATE-10

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related requirements: RFQX-CVS123-2-0134
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-UPDATE-11

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related requirements: RFQX-CVS123-2-0135
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-UPDATE-12

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related requirements: RFQX-CVS123-2-0163
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-UPDATE-13

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 21
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.
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related requirements: RFQX-CVS123-2-0170
Source document / section / page: source document page 21
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-UPDATE-14

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 35
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.
Why it matters: Update integrity protects ECU software authenticity over the lifecycle.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: A weak update path can defeat all runtime controls.
Related requirements: RFQX-CVS123-2-0270
Source document / section / page: source document page 35
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-01

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 43
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-3299216-1-0226
Source document / section / page: source document page 43
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-03

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 14
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS123-2-0093
Source document / section / page: source document page 14
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-04

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 17
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS123-2-0125
Source document / section / page: source document page 17
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-05

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS123-2-0138
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-06

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS123-2-0141
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-07

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 19
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS123-2-0144
Source document / section / page: source document page 19
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-08

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 19
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS123-2-0148
Source document / section / page: source document page 19
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-09

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 26
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS123-2-0219
Source document / section / page: source document page 26
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-10

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS123-2-0248
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-11

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 40
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS123-2-0318
Source document / section / page: source document page 40
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-12

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 40
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS123-2-0321
Source document / section / page: source document page 40
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-13

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 5
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS151-0017
Source document / section / page: source document page 5
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-14

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 6
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS151-0024
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-15

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 6
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS151-0026
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-16

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 6
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS154-0022
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-17

Priority: P3
Status: Reclassified as Assumption
Source of question: source document page 6
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS154-0023
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-18

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS31-0082
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-19

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 18
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS31-0091
Source document / section / page: source document page 18
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-20

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 19
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS31-0097
Source document / section / page: source document page 19
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-21

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 20
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS31-0108
Source document / section / page: source document page 20
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-22

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 23
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS31-0149
Source document / section / page: source document page 23
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-23

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS31-0150
Source document / section / page: source document page 23
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BACKEND-24

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 30
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.
Why it matters: Offboard systems influence update, evidence, monitoring, and response.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Operational responsibilities may fall between OEM and supplier.
Related requirements: RFQX-CVS31-0243
Source document / section / page: source document page 30
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-OPS-01

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 8
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.
Why it matters: Lifecycle security depends on clear operational ownership.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Post-release risks may have no owner or evidence path.
Related requirements: RFQX-3299216-1-0020
Source document / section / page: source document page 8
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-EVIDENCE-01

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 29
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.
Why it matters: Customer review needs trustworthy evidence, not only generated reports.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Compliance discussion may stall because evidence authority is unclear.
Related requirements: RFQX-3299216-1-0156
Source document / section / page: source document page 29
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-EVIDENCE-02

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 25
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.
Why it matters: Customer review needs trustworthy evidence, not only generated reports.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Compliance discussion may stall because evidence authority is unclear.
Related requirements: RFQX-CVS123-2-0212
Source document / section / page: source document page 25
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-EVIDENCE-03

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 38
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.
Why it matters: Customer review needs trustworthy evidence, not only generated reports.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Compliance discussion may stall because evidence authority is unclear.
Related requirements: RFQX-CVS123-2-0301
Source document / section / page: source document page 38
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-EVIDENCE-04

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 40
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.
Why it matters: Customer review needs trustworthy evidence, not only generated reports.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Compliance discussion may stall because evidence authority is unclear.
Related requirements: RFQX-CVS123-2-0314
Source document / section / page: source document page 40
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-EVIDENCE-05

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 4
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.
Why it matters: Customer review needs trustworthy evidence, not only generated reports.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Compliance discussion may stall because evidence authority is unclear.
Related requirements: RFQX-CVS154-0006
Source document / section / page: source document page 4
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-EVIDENCE-06

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 6
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.
Why it matters: Customer review needs trustworthy evidence, not only generated reports.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Compliance discussion may stall because evidence authority is unclear.
Related requirements: RFQX-CVS154-0019
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-EVIDENCE-07

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 6
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.
Why it matters: Customer review needs trustworthy evidence, not only generated reports.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Compliance discussion may stall because evidence authority is unclear.
Related requirements: RFQX-CVS154-0020
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-EVIDENCE-08

Priority: P3
Status: Reclassified as Informational
Source of question: source document page 6
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.
Why it matters: Customer review needs trustworthy evidence, not only generated reports.
Required customer decision: 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.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Compliance discussion may stall because evidence authority is unclear.
Related requirements: RFQX-CVS154-0024
Source document / section / page: source document page 6
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

Clarification Closure History

Clarification Closure Report

Generated: 2026-06-22T11:41:04+00:00

Questions evaluated: 472
Answered by additional PDF: 0
Partially answered by additional PDF: 0
Introduced by additional PDF: 52
Still open / customer decision needed: 472

Question Statuses

CQ-BOUNDARY-03

Priority: P1
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00003
Source document: source document page 3
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-05

Priority: P1
Baseline question ID: CQ-BOUNDARY-02
Previous status: Not Applicable
Source of question: Pre-additional baseline
Original 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.
New status: Still Requires Customer Decision
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00011
Source document: source document page 5
Closure decision: Still Requires Customer Decision
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-127

Priority: P1
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00732
Source document: source document page 6
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-158

Priority: P1
Baseline question ID: CQ-BOUNDARY-122
Previous status: Not Applicable
Source of question: Pre-additional baseline
Original 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.
New status: Still Requires Customer Decision
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00973
Source document: source document page 52
Closure decision: Still Requires Customer Decision
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-199

Priority: P1
Baseline question ID: CQ-BOUNDARY-163
Previous status: Not Applicable
Source of question: Pre-additional baseline
Original 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.
New status: Still Requires Customer Decision
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01321
Source document: source document page 9
Closure decision: Still Requires Customer Decision
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-201

Priority: P1
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01339
Source document: source document page 4
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-01

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00001
Source document: source document page 3
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-02

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00002
Source document: source document page 3
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-04

Priority: P3
Baseline question ID: CQ-BOUNDARY-01
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00006
Source document: source document page 5
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-06

Priority: P3
Baseline question ID: CQ-BOUNDARY-03
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_SEC_0040
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-07

Priority: P3
Baseline question ID: CQ-BOUNDARY-04
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_SEC_0041
Source document: source document page 7
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-08

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00070
Source document: source document page 4
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-09

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00113
Source document: source document page 12
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-10

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00115
Source document: source document page 12
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-100

Priority: P3
Baseline question ID: CQ-BOUNDARY-64
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00522
Source document: source document page 19
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-101

Priority: P3
Baseline question ID: CQ-BOUNDARY-65
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00523
Source document: source document page 19
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-102

Priority: P3
Baseline question ID: CQ-BOUNDARY-66
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00525
Source document: source document page 19
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-103

Priority: P3
Baseline question ID: CQ-BOUNDARY-67
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00526
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-104

Priority: P3
Baseline question ID: CQ-BOUNDARY-68
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00527
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-105

Priority: P3
Baseline question ID: CQ-BOUNDARY-69
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00531
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-106

Priority: P3
Baseline question ID: CQ-BOUNDARY-70
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00532
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-107

Priority: P3
Baseline question ID: CQ-BOUNDARY-71
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00534
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-108

Priority: P3
Baseline question ID: CQ-BOUNDARY-72
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00536
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-109

Priority: P3
Baseline question ID: CQ-BOUNDARY-38
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00538
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-11

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00194
Source document: source document page 25
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-110

Priority: P3
Baseline question ID: CQ-BOUNDARY-74
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00550
Source document: source document page 21
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-111

Priority: P3
Baseline question ID: CQ-BOUNDARY-75
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00556
Source document: source document page 21
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-112

Priority: P3
Baseline question ID: CQ-BOUNDARY-76
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00567
Source document: source document page 22
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-113

Priority: P3
Baseline question ID: CQ-BOUNDARY-77
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00586
Source document: source document page 25
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-114

Priority: P3
Baseline question ID: CQ-BOUNDARY-78
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00625
Source document: source document page 31
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-115

Priority: P3
Baseline question ID: CQ-BOUNDARY-79
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00629
Source document: source document page 32
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-116

Priority: P3
Baseline question ID: CQ-BOUNDARY-80
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00631
Source document: source document page 32
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-117

Priority: P3
Baseline question ID: CQ-BOUNDARY-81
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00635
Source document: source document page 32
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-118

Priority: P3
Baseline question ID: CQ-BOUNDARY-82
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00640
Source document: source document page 34
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-119

Priority: P3
Baseline question ID: CQ-BOUNDARY-83
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00648
Source document: source document page 35
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-12

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00197
Source document: source document page 25
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-120

Priority: P3
Baseline question ID: CQ-BOUNDARY-84
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00659
Source document: source document page 36
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-121

Priority: P3
Baseline question ID: CQ-BOUNDARY-85
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00667
Source document: source document page 37
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-122

Priority: P3
Baseline question ID: CQ-BOUNDARY-86
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00700
Source document: source document page 41
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-123

Priority: P3
Baseline question ID: CQ-BOUNDARY-87
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00703
Source document: source document page 41
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-124

Priority: P3
Baseline question ID: CQ-BOUNDARY-88
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00720
Source document: source document page 42
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-125

Priority: P3
Baseline question ID: CQ-BOUNDARY-89
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00721
Source document: source document page 42
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-126

Priority: P3
Baseline question ID: CQ-BOUNDARY-90
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00729
Source document: source document page 2
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-128

Priority: P3
Baseline question ID: CQ-BOUNDARY-92
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00737
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-129

Priority: P3
Baseline question ID: CQ-BOUNDARY-93
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00748
Source document: source document page 9
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-13

Priority: P3
Baseline question ID: CQ-BOUNDARY-06
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00208
Source document: source document page 27
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-130

Priority: P3
Baseline question ID: CQ-BOUNDARY-94
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0234
Source document: source document page 12
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-131

Priority: P3
Baseline question ID: CQ-BOUNDARY-95
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00768
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-132

Priority: P3
Baseline question ID: CQ-BOUNDARY-96
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00789
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-133

Priority: P3
Baseline question ID: CQ-BOUNDARY-97
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00793
Source document: source document page 22
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-134

Priority: P3
Baseline question ID: CQ-BOUNDARY-98
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00794
Source document: source document page 22
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-135

Priority: P3
Baseline question ID: CQ-BOUNDARY-99
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0041
Source document: source document page 23
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-136

Priority: P3
Baseline question ID: CQ-BOUNDARY-100
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0049
Source document: source document page 25
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-137

Priority: P3
Baseline question ID: CQ-BOUNDARY-101
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0310_6
Source document: source document page 28
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-138

Priority: P3
Baseline question ID: CQ-BOUNDARY-102
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0316_12
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-139

Priority: P3
Baseline question ID: CQ-BOUNDARY-103
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0320_16
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-14

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00224
Source document: source document page 29
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-140

Priority: P3
Baseline question ID: CQ-BOUNDARY-104
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0322_18
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-141

Priority: P3
Baseline question ID: CQ-BOUNDARY-105
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0326_22
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-142

Priority: P3
Baseline question ID: CQ-BOUNDARY-106
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0328_24
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-143

Priority: P3
Baseline question ID: CQ-BOUNDARY-107
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0329_25
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-144

Priority: P3
Baseline question ID: CQ-BOUNDARY-108
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0330_26
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-145

Priority: P3
Baseline question ID: CQ-BOUNDARY-109
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0331_27
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-146

Priority: P3
Baseline question ID: CQ-BOUNDARY-110
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0332_28
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-147

Priority: P3
Baseline question ID: CQ-BOUNDARY-111
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0333_29
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-148

Priority: P3
Baseline question ID: CQ-BOUNDARY-112
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0334_30
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-149

Priority: P3
Baseline question ID: CQ-BOUNDARY-113
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0335_31
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-15

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00225
Source document: source document page 29
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-150

Priority: P3
Baseline question ID: CQ-BOUNDARY-114
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0336_32
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-151

Priority: P3
Baseline question ID: CQ-BOUNDARY-115
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0337_33
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-152

Priority: P3
Baseline question ID: CQ-BOUNDARY-116
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00870
Source document: source document page 32
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-153

Priority: P3
Baseline question ID: CQ-BOUNDARY-117
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0064
Source document: source document page 33
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-154

Priority: P3
Baseline question ID: CQ-BOUNDARY-118
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00900
Source document: source document page 35
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-155

Priority: P3
Baseline question ID: CQ-BOUNDARY-119
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00908
Source document: source document page 37
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-156

Priority: P3
Baseline question ID: CQ-BOUNDARY-120
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0095
Source document: source document page 42
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-157

Priority: P3
Baseline question ID: CQ-BOUNDARY-121
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00967
Source document: source document page 49
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-159

Priority: P3
Baseline question ID: CQ-BOUNDARY-123
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0302
Source document: source document page 63
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-16

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00264
Source document: source document page 38
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-160

Priority: P3
Baseline question ID: CQ-BOUNDARY-124
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01053
Source document: source document page 66
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-161

Priority: P3
Baseline question ID: CQ-BOUNDARY-125
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01071
Source document: source document page 69
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-162

Priority: P3
Baseline question ID: CQ-BOUNDARY-126
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0169
Source document: source document page 74
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-163

Priority: P3
Baseline question ID: CQ-BOUNDARY-127
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01146
Source document: source document page 82
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-164

Priority: P3
Baseline question ID: CQ-BOUNDARY-128
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01193
Source document: source document page 1
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-165

Priority: P3
Baseline question ID: CQ-BOUNDARY-129
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01197
Source document: source document page 4
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-166

Priority: P3
Baseline question ID: CQ-BOUNDARY-130
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01199
Source document: source document page 4
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-167

Priority: P3
Baseline question ID: CQ-BOUNDARY-131
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01200
Source document: source document page 4
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-168

Priority: P3
Baseline question ID: CQ-BOUNDARY-132
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01201
Source document: source document page 4
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-169

Priority: P3
Baseline question ID: CQ-BOUNDARY-133
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01202
Source document: source document page 4
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-17

Priority: P3
Baseline question ID: CQ-BOUNDARY-08
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00289
Source document: source document page 41
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-170

Priority: P3
Baseline question ID: CQ-BOUNDARY-134
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01204
Source document: source document page 5
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-171

Priority: P3
Baseline question ID: CQ-BOUNDARY-135
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01205
Source document: source document page 5
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-172

Priority: P3
Baseline question ID: CQ-BOUNDARY-136
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01213
Source document: source document page 5
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-173

Priority: P3
Baseline question ID: CQ-BOUNDARY-137
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01214
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-174

Priority: P3
Baseline question ID: CQ-BOUNDARY-138
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01217
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-175

Priority: P3
Baseline question ID: CQ-BOUNDARY-139
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01219
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-176

Priority: P3
Baseline question ID: CQ-BOUNDARY-140
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01221
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-177

Priority: P3
Baseline question ID: CQ-BOUNDARY-141
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01223
Source document: source document page 8
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-178

Priority: P3
Baseline question ID: CQ-BOUNDARY-142
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01230
Source document: source document page 8
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-179

Priority: P3
Baseline question ID: CQ-BOUNDARY-143
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01231
Source document: source document page 8
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-18

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00290
Source document: source document page 43
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-180

Priority: P3
Baseline question ID: CQ-BOUNDARY-144
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01234
Source document: source document page 8
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-181

Priority: P3
Baseline question ID: CQ-BOUNDARY-145
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01235
Source document: source document page 8
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-182

Priority: P3
Baseline question ID: CQ-BOUNDARY-146
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01238
Source document: source document page 9
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-183

Priority: P3
Baseline question ID: CQ-BOUNDARY-147
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01239
Source document: source document page 9
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-184

Priority: P3
Baseline question ID: CQ-BOUNDARY-148
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01244
Source document: source document page 9
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-185

Priority: P3
Baseline question ID: CQ-BOUNDARY-149
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01248
Source document: source document page 10
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-186

Priority: P3
Baseline question ID: CQ-BOUNDARY-150
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01251
Source document: source document page 11
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-187

Priority: P3
Baseline question ID: CQ-BOUNDARY-151
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01253
Source document: source document page 11
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-188

Priority: P3
Baseline question ID: CQ-BOUNDARY-152
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01255
Source document: source document page 12
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-189

Priority: P3
Baseline question ID: CQ-BOUNDARY-153
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01261
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-19

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00296
Source document: source document page 43
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-190

Priority: P3
Baseline question ID: CQ-BOUNDARY-154
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01262
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-191

Priority: P3
Baseline question ID: CQ-BOUNDARY-155
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01264
Source document: source document page 16
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-192

Priority: P3
Baseline question ID: CQ-BOUNDARY-156
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01282
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-193

Priority: P3
Baseline question ID: CQ-BOUNDARY-157
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01287
Source document: source document page 1
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-194

Priority: P3
Baseline question ID: CQ-BOUNDARY-158
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01291
Source document: source document page 4
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-195

Priority: P3
Baseline question ID: CQ-BOUNDARY-159
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01293
Source document: source document page 5
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-196

Priority: P3
Baseline question ID: CQ-BOUNDARY-160
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01314
Source document: source document page 7
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-197

Priority: P3
Baseline question ID: CQ-BOUNDARY-161
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01316
Source document: source document page 7
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-198

Priority: P3
Baseline question ID: CQ-BOUNDARY-162
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01319
Source document: source document page 9
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-20

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00301
Source document: source document page 43
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-200

Priority: P3
Baseline question ID: CQ-BOUNDARY-164
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01335
Source document: source document page 3
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-202

Priority: P3
Baseline question ID: CQ-BOUNDARY-165
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01346
Source document: source document page 7
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-203

Priority: P3
Baseline question ID: CQ-BOUNDARY-166
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01356
Source document: source document page 9
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-204

Priority: P3
Baseline question ID: CQ-BOUNDARY-167
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01365
Source document: source document page 11
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-205

Priority: P3
Baseline question ID: CQ-BOUNDARY-168
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01368
Source document: source document page 11
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-206

Priority: P3
Baseline question ID: CQ-BOUNDARY-169
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01372
Source document: source document page 11
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-207

Priority: P3
Baseline question ID: CQ-BOUNDARY-170
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01383
Source document: source document page 13
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-208

Priority: P3
Baseline question ID: CQ-BOUNDARY-171
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01385
Source document: source document page 13
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-209

Priority: P3
Baseline question ID: CQ-BOUNDARY-172
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01386
Source document: source document page 13
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-21

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00302
Source document: source document page 43
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-210

Priority: P3
Baseline question ID: CQ-BOUNDARY-173
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01397
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-211

Priority: P3
Baseline question ID: CQ-BOUNDARY-174
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01418
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-212

Priority: P3
Baseline question ID: CQ-BOUNDARY-175
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01419
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-213

Priority: P3
Baseline question ID: CQ-BOUNDARY-176
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01425
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-214

Priority: P3
Baseline question ID: CQ-BOUNDARY-177
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01440
Source document: source document page 19
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-215

Priority: P3
Baseline question ID: CQ-BOUNDARY-178
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01445
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-216

Priority: P3
Baseline question ID: CQ-BOUNDARY-179
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01448
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-217

Priority: P3
Baseline question ID: CQ-BOUNDARY-180
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01456
Source document: source document page 21
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-218

Priority: P3
Baseline question ID: CQ-BOUNDARY-181
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01459
Source document: source document page 21
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-219

Priority: P3
Baseline question ID: CQ-BOUNDARY-182
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01464
Source document: source document page 21
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-22

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00305
Source document: source document page 43
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-220

Priority: P3
Baseline question ID: CQ-BOUNDARY-180
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01465
Source document: source document page 21
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-221

Priority: P3
Baseline question ID: CQ-BOUNDARY-184
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01468
Source document: source document page 22
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-222

Priority: P3
Baseline question ID: CQ-BOUNDARY-185
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01469
Source document: source document page 22
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-223

Priority: P3
Baseline question ID: CQ-BOUNDARY-186
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01472
Source document: source document page 22
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-224

Priority: P3
Baseline question ID: CQ-BOUNDARY-187
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01473
Source document: source document page 22
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-225

Priority: P3
Baseline question ID: CQ-BOUNDARY-188
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01562
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-226

Priority: P3
Baseline question ID: CQ-BOUNDARY-189
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01563
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-227

Priority: P3
Baseline question ID: CQ-BOUNDARY-190
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01577
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-228

Priority: P3
Baseline question ID: CQ-BOUNDARY-191
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01578
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-229

Priority: P3
Baseline question ID: CQ-BOUNDARY-192
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01587
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-23

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00307
Source document: source document page 43
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-230

Priority: P3
Baseline question ID: CQ-BOUNDARY-193
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01589
Source document: source document page 2
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-231

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01592
Source document: source document page 4
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-232

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01593
Source document: source document page 4
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-233

Priority: P3
Baseline question ID: CQ-BOUNDARY-194
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01600
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-234

Priority: P3
Baseline question ID: CQ-BOUNDARY-195
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01602
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-235

Priority: P3
Baseline question ID: CQ-BOUNDARY-196
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01632
Source document: source document page 10
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-236

Priority: P3
Baseline question ID: CQ-BOUNDARY-197
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01636
Source document: source document page 10
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-237

Priority: P3
Baseline question ID: CQ-BOUNDARY-198
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01637
Source document: source document page 10
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-238

Priority: P3
Baseline question ID: CQ-BOUNDARY-199
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01639
Source document: source document page 10
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-239

Priority: P3
Baseline question ID: CQ-BOUNDARY-200
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01649
Source document: source document page 12
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-24

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00308
Source document: source document page 43
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-240

Priority: P3
Baseline question ID: CQ-BOUNDARY-201
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01673
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-241

Priority: P3
Baseline question ID: CQ-BOUNDARY-202
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01699
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-242

Priority: P3
Baseline question ID: CQ-BOUNDARY-203
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01701
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-243

Priority: P3
Baseline question ID: CQ-BOUNDARY-204
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01704
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-244

Priority: P3
Baseline question ID: CQ-BOUNDARY-205
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01725
Source document: source document page 21
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-25

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00309
Source document: source document page 43
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-26

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00313
Source document: source document page 44
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-27

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00314
Source document: source document page 44
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-28

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00315
Source document: source document page 44
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-29

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00317
Source document: source document page 44
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-30

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00318
Source document: source document page 44
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-31

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00324
Source document: source document page 47
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-32

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00333
Source document: source document page 47
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-33

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00334
Source document: source document page 47
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-34

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00335
Source document: source document page 47
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-35

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00336
Source document: source document page 47
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-36

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00337
Source document: source document page 47
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-37

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00338
Source document: source document page 47
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-38

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00339
Source document: source document page 47
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-39

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00340
Source document: source document page 47
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-40

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00341
Source document: source document page 47
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-41

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00342
Source document: source document page 47
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-42

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00343
Source document: source document page 47
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-43

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00344
Source document: source document page 47
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-44

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00345
Source document: source document page 47
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-45

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00351
Source document: source document page 50
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-46

Priority: P3
Baseline question ID: CQ-BOUNDARY-10
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00368
Source document: source document page 52
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-47

Priority: P3
Baseline question ID: CQ-BOUNDARY-11
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00376
Source document: source document page 61
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-48

Priority: P3
Baseline question ID: CQ-BOUNDARY-12
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00377
Source document: source document page 1
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-49

Priority: P3
Baseline question ID: CQ-BOUNDARY-13
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00381
Source document: source document page 4
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-50

Priority: P3
Baseline question ID: CQ-BOUNDARY-14
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00382
Source document: source document page 4
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-51

Priority: P3
Baseline question ID: CQ-BOUNDARY-15
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00383
Source document: source document page 4
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-52

Priority: P3
Baseline question ID: CQ-BOUNDARY-16
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00385
Source document: source document page 4
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-53

Priority: P3
Baseline question ID: CQ-BOUNDARY-17
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00388
Source document: source document page 4
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-54

Priority: P3
Baseline question ID: CQ-BOUNDARY-18
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00391
Source document: source document page 5
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-55

Priority: P3
Baseline question ID: CQ-BOUNDARY-19
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00392
Source document: source document page 5
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-56

Priority: P3
Baseline question ID: CQ-BOUNDARY-20
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00393
Source document: source document page 5
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-57

Priority: P3
Baseline question ID: CQ-BOUNDARY-21
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00401
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-58

Priority: P3
Baseline question ID: CQ-BOUNDARY-22
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00403
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-59

Priority: P3
Baseline question ID: CQ-BOUNDARY-23
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00409
Source document: source document page 8
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-60

Priority: P3
Baseline question ID: CQ-BOUNDARY-24
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00421
Source document: source document page 9
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-61

Priority: P3
Baseline question ID: CQ-BOUNDARY-25
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00430
Source document: source document page 10
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-62

Priority: P3
Baseline question ID: CQ-BOUNDARY-26
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00436
Source document: source document page 11
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-63

Priority: P3
Baseline question ID: CQ-BOUNDARY-27
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00439
Source document: source document page 11
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-64

Priority: P3
Baseline question ID: CQ-BOUNDARY-28
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00449
Source document: source document page 12
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-65

Priority: P3
Baseline question ID: CQ-BOUNDARY-29
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00450
Source document: source document page 12
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-66

Priority: P3
Baseline question ID: CQ-BOUNDARY-30
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00456
Source document: source document page 12
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-67

Priority: P3
Baseline question ID: CQ-BOUNDARY-31
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00457
Source document: source document page 13
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-68

Priority: P3
Baseline question ID: CQ-BOUNDARY-32
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00458
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-69

Priority: P3
Baseline question ID: CQ-BOUNDARY-33
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00460
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-70

Priority: P3
Baseline question ID: CQ-BOUNDARY-34
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00462
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-71

Priority: P3
Baseline question ID: CQ-BOUNDARY-35
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00463
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-72

Priority: P3
Baseline question ID: CQ-BOUNDARY-36
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00465
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-73

Priority: P3
Baseline question ID: CQ-BOUNDARY-37
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00466
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-74

Priority: P3
Baseline question ID: CQ-BOUNDARY-38
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00467
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-75

Priority: P3
Baseline question ID: CQ-BOUNDARY-38
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00472
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-76

Priority: P3
Baseline question ID: CQ-BOUNDARY-40
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00474
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-77

Priority: P3
Baseline question ID: CQ-BOUNDARY-41
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00475
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-78

Priority: P3
Baseline question ID: CQ-BOUNDARY-42
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00476
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-79

Priority: P3
Baseline question ID: CQ-BOUNDARY-43
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00477
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-80

Priority: P3
Baseline question ID: CQ-BOUNDARY-44
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00478
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-81

Priority: P3
Baseline question ID: CQ-BOUNDARY-45
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00479
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-82

Priority: P3
Baseline question ID: CQ-BOUNDARY-46
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00480
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-83

Priority: P3
Baseline question ID: CQ-BOUNDARY-47
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00482
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-84

Priority: P3
Baseline question ID: CQ-BOUNDARY-48
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00483
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-85

Priority: P3
Baseline question ID: CQ-BOUNDARY-49
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00484
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-86

Priority: P3
Baseline question ID: CQ-BOUNDARY-50
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00487
Source document: source document page 16
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-87

Priority: P3
Baseline question ID: CQ-BOUNDARY-51
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00489
Source document: source document page 16
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-88

Priority: P3
Baseline question ID: CQ-BOUNDARY-52
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00491
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-89

Priority: P3
Baseline question ID: CQ-BOUNDARY-53
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00492
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-90

Priority: P3
Baseline question ID: CQ-BOUNDARY-54
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00493
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-91

Priority: P3
Baseline question ID: CQ-BOUNDARY-55
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00494
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-92

Priority: P3
Baseline question ID: CQ-BOUNDARY-56
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00498
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-93

Priority: P3
Baseline question ID: CQ-BOUNDARY-57
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00505
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-94

Priority: P3
Baseline question ID: CQ-BOUNDARY-58
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00506
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-95

Priority: P3
Baseline question ID: CQ-BOUNDARY-59
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00507
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-96

Priority: P3
Baseline question ID: CQ-BOUNDARY-60
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00508
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-97

Priority: P3
Baseline question ID: CQ-BOUNDARY-61
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00509
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-98

Priority: P3
Baseline question ID: CQ-BOUNDARY-62
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00515
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BOUNDARY-99

Priority: P3
Baseline question ID: CQ-BOUNDARY-63
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00519
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-01

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00072
Source document: source document page 4
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-02

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00073
Source document: source document page 4
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-03

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00090
Source document: source document page 9
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-04

Priority: P3
Baseline question ID: CQ-INTERFACE-01
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00120
Source document: source document page 13
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-05

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00147
Source document: source document page 20
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-06

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00240
Source document: source document page 34
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-07

Priority: P3
Baseline question ID: CQ-INTERFACE-02
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00384
Source document: source document page 4
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-08

Priority: P3
Baseline question ID: CQ-INTERFACE-03
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00461
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-09

Priority: P3
Baseline question ID: CQ-INTERFACE-04
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00656
Source document: source document page 35
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-10

Priority: P3
Baseline question ID: CQ-INTERFACE-05
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00669
Source document: source document page 37
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-11

Priority: P3
Baseline question ID: CQ-INTERFACE-06
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00722
Source document: source document page 42
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-12

Priority: P3
Baseline question ID: CQ-INTERFACE-07
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0314_10
Source document: source document page 28
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-13

Priority: P3
Baseline question ID: CQ-INTERFACE-08
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00921
Source document: source document page 38
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-14

Priority: P3
Baseline question ID: CQ-INTERFACE-09
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0303
Source document: source document page 63
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-15

Priority: P3
Baseline question ID: CQ-INTERFACE-10
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01084
Source document: source document page 72
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-16

Priority: P3
Baseline question ID: CQ-INTERFACE-11
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01207
Source document: source document page 5
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-17

Priority: P3
Baseline question ID: CQ-INTERFACE-12
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01256
Source document: source document page 12
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-18

Priority: P3
Baseline question ID: CQ-INTERFACE-13
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01402
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-19

Priority: P3
Baseline question ID: CQ-INTERFACE-14
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01405
Source document: source document page 16
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-20

Priority: P3
Baseline question ID: CQ-INTERFACE-15
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01597
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-21

Priority: P3
Baseline question ID: CQ-INTERFACE-16
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01598
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-22

Priority: P3
Baseline question ID: CQ-INTERFACE-17
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01605
Source document: source document page 7
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-23

Priority: P3
Baseline question ID: CQ-INTERFACE-18
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01609
Source document: source document page 7
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-24

Priority: P3
Baseline question ID: CQ-INTERFACE-19
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01610
Source document: source document page 7
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-25

Priority: P3
Baseline question ID: CQ-INTERFACE-20
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01611
Source document: source document page 7
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-26

Priority: P3
Baseline question ID: CQ-INTERFACE-21
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01619
Source document: source document page 8
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-27

Priority: P3
Baseline question ID: CQ-INTERFACE-22
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01621
Source document: source document page 8
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-28

Priority: P3
Baseline question ID: CQ-INTERFACE-23
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01624
Source document: source document page 8
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-29

Priority: P3
Baseline question ID: CQ-INTERFACE-24
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01625
Source document: source document page 8
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-30

Priority: P3
Baseline question ID: CQ-INTERFACE-25
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01626
Source document: source document page 9
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-31

Priority: P3
Baseline question ID: CQ-INTERFACE-26
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01628
Source document: source document page 9
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-32

Priority: P3
Baseline question ID: CQ-INTERFACE-27
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01629
Source document: source document page 9
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-33

Priority: P3
Baseline question ID: CQ-INTERFACE-28
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01630
Source document: source document page 9
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-34

Priority: P3
Baseline question ID: CQ-INTERFACE-29
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01642
Source document: source document page 11
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-35

Priority: P3
Baseline question ID: CQ-INTERFACE-30
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01647
Source document: source document page 11
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-36

Priority: P3
Baseline question ID: CQ-INTERFACE-31
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01648
Source document: source document page 11
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-37

Priority: P3
Baseline question ID: CQ-INTERFACE-32
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01650
Source document: source document page 12
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-38

Priority: P3
Baseline question ID: CQ-INTERFACE-33
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01654
Source document: source document page 12
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-39

Priority: P3
Baseline question ID: CQ-INTERFACE-34
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01659
Source document: source document page 12
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-40

Priority: P3
Baseline question ID: CQ-INTERFACE-35
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01674
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-41

Priority: P3
Baseline question ID: CQ-INTERFACE-36
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01676
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-42

Priority: P3
Baseline question ID: CQ-INTERFACE-37
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01677
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-43

Priority: P3
Baseline question ID: CQ-INTERFACE-38
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01681
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-44

Priority: P3
Baseline question ID: CQ-INTERFACE-39
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01684
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-45

Priority: P3
Baseline question ID: CQ-INTERFACE-40
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01685
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-46

Priority: P3
Baseline question ID: CQ-INTERFACE-41
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01700
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-47

Priority: P3
Baseline question ID: CQ-INTERFACE-42
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01702
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-48

Priority: P3
Baseline question ID: CQ-INTERFACE-43
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01703
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-49

Priority: P3
Baseline question ID: CQ-INTERFACE-44
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01705
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-50

Priority: P3
Baseline question ID: CQ-INTERFACE-45
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01714
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-51

Priority: P3
Baseline question ID: CQ-INTERFACE-46
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01716
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-52

Priority: P3
Baseline question ID: CQ-INTERFACE-47
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01719
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-53

Priority: P3
Baseline question ID: CQ-INTERFACE-48
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01721
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-54

Priority: P3
Baseline question ID: CQ-INTERFACE-49
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01722
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-55

Priority: P3
Baseline question ID: CQ-INTERFACE-50
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01723
Source document: source document page 21
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-56

Priority: P3
Baseline question ID: CQ-INTERFACE-51
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01724
Source document: source document page 21
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-57

Priority: P3
Baseline question ID: CQ-INTERFACE-52
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01735
Source document: source document page 23
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-58

Priority: P3
Baseline question ID: CQ-INTERFACE-53
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01736
Source document: source document page 23
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-59

Priority: P3
Baseline question ID: CQ-INTERFACE-54
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01737
Source document: source document page 23
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-60

Priority: P3
Baseline question ID: CQ-INTERFACE-55
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01740
Source document: source document page 23
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-61

Priority: P3
Baseline question ID: CQ-INTERFACE-56
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01752
Source document: source document page 28
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-62

Priority: P3
Baseline question ID: CQ-INTERFACE-57
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01756
Source document: source document page 28
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-63

Priority: P3
Baseline question ID: CQ-INTERFACE-58
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01757
Source document: source document page 28
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-64

Priority: P3
Baseline question ID: CQ-INTERFACE-59
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01758
Source document: source document page 28
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-65

Priority: P3
Baseline question ID: CQ-INTERFACE-60
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01768
Source document: source document page 28
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-66

Priority: P3
Baseline question ID: CQ-INTERFACE-61
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01774
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-67

Priority: P3
Baseline question ID: CQ-INTERFACE-62
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01787
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-68

Priority: P3
Baseline question ID: CQ-INTERFACE-63
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01789
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-INTERFACE-69

Priority: P3
Baseline question ID: CQ-INTERFACE-64
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01790
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-01

Priority: P3
Baseline question ID: CQ-DIAG-01
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00389
Source document: source document page 4
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-02

Priority: P3
Baseline question ID: CQ-DIAG-02
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0051
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-03

Priority: P3
Baseline question ID: CQ-DIAG-03
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00464
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-04

Priority: P3
Baseline question ID: CQ-DIAG-04
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00468
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-05

Priority: P3
Baseline question ID: CQ-DIAG-05
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00473
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-06

Priority: P3
Baseline question ID: CQ-DIAG-06
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00481
Source document: source document page 15
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-07

Priority: P3
Baseline question ID: CQ-DIAG-07
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00499
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-08

Priority: P3
Baseline question ID: CQ-DIAG-08
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00500
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-09

Priority: P3
Baseline question ID: CQ-DIAG-09
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0051
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-10

Priority: P3
Baseline question ID: CQ-DIAG-10
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00504
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-11

Priority: P3
Baseline question ID: CQ-DIAG-11
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00512
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-12

Priority: P3
Baseline question ID: CQ-DIAG-04
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00535
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-13

Priority: P3
Baseline question ID: CQ-DIAG-13
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00607
Source document: source document page 28
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-14

Priority: P3
Baseline question ID: CQ-DIAG-14
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00666
Source document: source document page 37
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-15

Priority: P3
Baseline question ID: CQ-DIAG-15
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00749
Source document: source document page 9
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-16

Priority: P3
Baseline question ID: CQ-DIAG-16
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0231
Source document: source document page 11
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-17

Priority: P3
Baseline question ID: CQ-DIAG-17
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0235
Source document: source document page 13
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-18

Priority: P3
Baseline question ID: CQ-DIAG-18
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0237
Source document: source document page 16
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-19

Priority: P3
Baseline question ID: CQ-DIAG-19
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0339
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-20

Priority: P3
Baseline question ID: CQ-DIAG-20
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0305_1
Source document: source document page 27
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-21

Priority: P3
Baseline question ID: CQ-DIAG-21
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00818
Source document: source document page 27
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-22

Priority: P3
Baseline question ID: CQ-DIAG-22
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0307_3
Source document: source document page 28
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-23

Priority: P3
Baseline question ID: CQ-DIAG-23
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0308_4
Source document: source document page 28
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-24

Priority: P3
Baseline question ID: CQ-DIAG-24
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0309_5
Source document: source document page 28
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-25

Priority: P3
Baseline question ID: CQ-DIAG-25
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0311_7
Source document: source document page 28
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-26

Priority: P3
Baseline question ID: CQ-DIAG-26
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0312_8
Source document: source document page 28
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-27

Priority: P3
Baseline question ID: CQ-DIAG-27
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0313_9
Source document: source document page 28
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-28

Priority: P3
Baseline question ID: CQ-DIAG-28
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0315_11
Source document: source document page 28
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-29

Priority: P3
Baseline question ID: CQ-DIAG-29
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0317_13
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-30

Priority: P3
Baseline question ID: CQ-DIAG-30
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0318_14
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-31

Priority: P3
Baseline question ID: CQ-DIAG-31
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0319_15
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-32

Priority: P3
Baseline question ID: CQ-DIAG-32
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0321_17
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-33

Priority: P3
Baseline question ID: CQ-DIAG-33
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0323_19
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-34

Priority: P3
Baseline question ID: CQ-DIAG-34
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0324_20
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-35

Priority: P3
Baseline question ID: CQ-DIAG-35
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0325_21
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-36

Priority: P3
Baseline question ID: CQ-DIAG-36
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0327_23
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-37

Priority: P3
Baseline question ID: CQ-DIAG-37
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0239
Source document: source document page 32
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-38

Priority: P3
Baseline question ID: CQ-DIAG-38
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00897
Source document: source document page 35
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-39

Priority: P3
Baseline question ID: CQ-DIAG-39
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0346
Source document: source document page 37
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-40

Priority: P3
Baseline question ID: CQ-DIAG-40
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0347
Source document: source document page 38
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-41

Priority: P3
Baseline question ID: CQ-DIAG-41
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0348
Source document: source document page 38
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-42

Priority: P3
Baseline question ID: CQ-DIAG-42
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0349
Source document: source document page 38
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-43

Priority: P3
Baseline question ID: CQ-DIAG-43
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0253
Source document: source document page 39
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-44

Priority: P3
Baseline question ID: CQ-DIAG-44
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0090
Source document: source document page 40
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-45

Priority: P3
Baseline question ID: CQ-DIAG-45
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0093
Source document: source document page 40
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-46

Priority: P3
Baseline question ID: CQ-DIAG-46
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0260
Source document: source document page 41
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-47

Priority: P3
Baseline question ID: CQ-DIAG-47
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0264
Source document: source document page 41
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-48

Priority: P3
Baseline question ID: CQ-DIAG-48
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0272
Source document: source document page 43
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-49

Priority: P3
Baseline question ID: CQ-DIAG-49
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0286
Source document: source document page 55
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-50

Priority: P3
Baseline question ID: CQ-DIAG-50
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0287
Source document: source document page 55
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-51

Priority: P3
Baseline question ID: CQ-DIAG-51
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00998
Source document: source document page 57
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-52

Priority: P3
Baseline question ID: CQ-DIAG-52
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0293
Source document: source document page 61
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-53

Priority: P3
Baseline question ID: CQ-DIAG-53
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0300
Source document: source document page 62
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-54

Priority: P3
Baseline question ID: CQ-DIAG-54
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01069
Source document: source document page 69
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-55

Priority: P3
Baseline question ID: CQ-DIAG-55
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01085
Source document: source document page 72
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-56

Priority: P3
Baseline question ID: CQ-DIAG-56
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01086
Source document: source document page 73
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-57

Priority: P3
Baseline question ID: CQ-DIAG-57
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01087
Source document: source document page 73
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-58

Priority: P3
Baseline question ID: CQ-DIAG-58
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01090
Source document: source document page 74
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-59

Priority: P3
Baseline question ID: CQ-DIAG-59
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01121
Source document: source document page 79
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-60

Priority: P3
Baseline question ID: CQ-DIAG-60
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01122
Source document: source document page 79
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-61

Priority: P3
Baseline question ID: CQ-DIAG-61
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01128
Source document: source document page 80
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-62

Priority: P3
Baseline question ID: CQ-DIAG-62
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01138
Source document: source document page 81
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-63

Priority: P3
Baseline question ID: CQ-DIAG-63
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0208
Source document: source document page 81
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-64

Priority: P3
Baseline question ID: CQ-DIAG-64
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0215
Source document: source document page 82
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-65

Priority: P3
Baseline question ID: CQ-DIAG-65
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0216
Source document: source document page 82
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-66

Priority: P3
Baseline question ID: CQ-DIAG-66
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0217
Source document: source document page 82
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-67

Priority: P3
Baseline question ID: CQ-DIAG-67
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01152
Source document: source document page 83
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-68

Priority: P3
Baseline question ID: CQ-DIAG-68
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0218
Source document: source document page 83
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-69

Priority: P3
Baseline question ID: CQ-DIAG-69
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0220
Source document: source document page 83
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-70

Priority: P3
Baseline question ID: CQ-DIAG-70
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0221
Source document: source document page 83
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-71

Priority: P3
Baseline question ID: CQ-DIAG-71
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0222
Source document: source document page 83
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-72

Priority: P3
Baseline question ID: CQ-DIAG-72
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0349
Source document: source document page 90
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-73

Priority: P3
Baseline question ID: CQ-DIAG-73
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0003
Source document: source document page 90
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-74

Priority: P3
Baseline question ID: CQ-DIAG-74
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01181
Source document: source document page 90
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-75

Priority: P3
Baseline question ID: CQ-DIAG-75
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0036
Source document: source document page 90
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-76

Priority: P3
Baseline question ID: CQ-DIAG-76
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0037
Source document: source document page 90
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-77

Priority: P3
Baseline question ID: CQ-DIAG-77
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0180
Source document: source document page 90
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-78

Priority: P3
Baseline question ID: CQ-DIAG-78
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0193
Source document: source document page 90
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-79

Priority: P3
Baseline question ID: CQ-DIAG-79
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ_UDS_0024
Source document: source document page 90
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-80

Priority: P3
Baseline question ID: CQ-DIAG-80
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01259
Source document: source document page 12
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-81

Priority: P3
Baseline question ID: CQ-DIAG-81
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01269
Source document: source document page 19
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-82

Priority: P3
Baseline question ID: CQ-DIAG-82
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01351
Source document: source document page 8
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-83

Priority: P3
Baseline question ID: CQ-DIAG-83
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01377
Source document: source document page 12
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-84

Priority: P3
Baseline question ID: CQ-DIAG-84
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01409
Source document: source document page 16
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-85

Priority: P3
Baseline question ID: CQ-DIAG-85
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01449
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-86

Priority: P3
Baseline question ID: CQ-DIAG-86
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01451
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-87

Priority: P3
Baseline question ID: CQ-DIAG-87
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01462
Source document: source document page 21
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-88

Priority: P3
Baseline question ID: CQ-DIAG-88
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01463
Source document: source document page 21
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-89

Priority: P3
Baseline question ID: CQ-DIAG-89
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01477
Source document: source document page 23
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-90

Priority: P3
Baseline question ID: CQ-DIAG-90
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01478
Source document: source document page 23
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-91

Priority: P3
Baseline question ID: CQ-DIAG-91
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01492
Source document: source document page 24
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-92

Priority: P3
Baseline question ID: CQ-DIAG-92
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01494
Source document: source document page 24
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-93

Priority: P3
Baseline question ID: CQ-DIAG-93
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01582
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-DIAG-94

Priority: P3
Baseline question ID: CQ-DIAG-94
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01604
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-UPDATE-01

Priority: P3
Baseline question ID: CQ-UPDATE-01
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00380
Source document: source document page 4
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-UPDATE-02

Priority: P3
Baseline question ID: CQ-UPDATE-02
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00452
Source document: source document page 12
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-UPDATE-03

Priority: P3
Baseline question ID: CQ-UPDATE-03
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00453
Source document: source document page 12
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-UPDATE-04

Priority: P3
Baseline question ID: CQ-UPDATE-04
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00459
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-UPDATE-05

Priority: P3
Baseline question ID: CQ-UPDATE-05
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00471
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-UPDATE-06

Priority: P3
Baseline question ID: CQ-UPDATE-06
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00485
Source document: source document page 16
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-UPDATE-07

Priority: P3
Baseline question ID: CQ-UPDATE-07
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00495
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-UPDATE-08

Priority: P3
Baseline question ID: CQ-UPDATE-08
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00496
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-UPDATE-09

Priority: P3
Baseline question ID: CQ-UPDATE-09
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00497
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-UPDATE-10

Priority: P3
Baseline question ID: CQ-UPDATE-10
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00510
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-UPDATE-11

Priority: P3
Baseline question ID: CQ-UPDATE-11
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00511
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-UPDATE-12

Priority: P3
Baseline question ID: CQ-UPDATE-12
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00539
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-UPDATE-13

Priority: P3
Baseline question ID: CQ-UPDATE-13
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00546
Source document: source document page 21
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-UPDATE-14

Priority: P3
Baseline question ID: CQ-UPDATE-14
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00646
Source document: source document page 35
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-PKI-01

Priority: P3
Baseline question ID: CQ-PKI-01
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00672
Source document: source document page 37
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-PKI-02

Priority: P3
Baseline question ID: CQ-PKI-02
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01367
Source document: source document page 11
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-PKI-03

Priority: P3
Baseline question ID: CQ-PKI-03
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01388
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-PKI-04

Priority: P3
Baseline question ID: CQ-PKI-04
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01390
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-PKI-05

Priority: P3
Baseline question ID: CQ-PKI-05
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01460
Source document: source document page 21
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-PKI-06

Priority: P3
Baseline question ID: CQ-PKI-06
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01497
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-PKI-07

Priority: P3
Baseline question ID: CQ-PKI-07
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01530
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-PKI-08

Priority: P3
Baseline question ID: CQ-PKI-08
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01544
Source document: source document page 29
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-PKI-09

Priority: P3
Baseline question ID: CQ-PKI-09
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01579
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-HSM-01

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00214
Source document: source document page 28
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-HSM-02

Priority: P3
Baseline question ID: CQ-HSM-01
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00503
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-HSM-03

Priority: P3
Baseline question ID: CQ-HSM-02
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00521
Source document: source document page 19
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-HSM-04

Priority: P3
Baseline question ID: CQ-DIAG-51
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00578
Source document: source document page 24
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-HSM-05

Priority: P3
Baseline question ID: CQ-DIAG-54
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00633
Source document: source document page 32
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-HSM-06

Priority: P3
Baseline question ID: CQ-HSM-05
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00691
Source document: source document page 40
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-HSM-07

Priority: P3
Baseline question ID: CQ-HSM-06
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00708
Source document: source document page 41
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-HSM-08

Priority: P3
Baseline question ID: CQ-HSM-07
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00724
Source document: source document page 47
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-02

Priority: P2
Baseline question ID: CQ-BACKEND-01
Previous status: Not Applicable
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00431
Source document: source document page 10
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-01

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00293
Source document: source document page 43
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-03

Priority: P3
Baseline question ID: CQ-BACKEND-02
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00469
Source document: source document page 14
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-04

Priority: P3
Baseline question ID: CQ-BACKEND-03
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00501
Source document: source document page 17
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-05

Priority: P3
Baseline question ID: CQ-BACKEND-04
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00514
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-06

Priority: P3
Baseline question ID: CQ-BACKEND-05
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00517
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-07

Priority: P3
Baseline question ID: CQ-BACKEND-06
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00520
Source document: source document page 19
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-08

Priority: P3
Baseline question ID: CQ-BACKEND-07
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00524
Source document: source document page 19
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-09

Priority: P3
Baseline question ID: CQ-BACKEND-08
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00595
Source document: source document page 26
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-10

Priority: P3
Baseline question ID: CQ-BACKEND-09
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00624
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-11

Priority: P3
Baseline question ID: CQ-BACKEND-10
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00694
Source document: source document page 40
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-12

Priority: P3
Baseline question ID: CQ-BACKEND-11
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00697
Source document: source document page 40
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-13

Priority: P3
Baseline question ID: CQ-BACKEND-12
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01209
Source document: source document page 5
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-14

Priority: P3
Baseline question ID: CQ-BACKEND-13
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01216
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-15

Priority: P3
Baseline question ID: CQ-BACKEND-14
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01218
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-16

Priority: P3
Baseline question ID: CQ-BACKEND-15
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01308
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-17

Priority: P3
Baseline question ID: CQ-BACKEND-16
Previous status: Reclassified as Assumption
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01309
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-18

Priority: P3
Baseline question ID: CQ-BACKEND-17
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01415
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-19

Priority: P3
Baseline question ID: CQ-BACKEND-18
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01424
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-20

Priority: P3
Baseline question ID: CQ-BACKEND-19
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01430
Source document: source document page 19
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-21

Priority: P3
Baseline question ID: CQ-BACKEND-20
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01441
Source document: source document page 20
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-22

Priority: P3
Baseline question ID: CQ-BACKEND-21
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01482
Source document: source document page 23
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-23

Priority: P3
Baseline question ID: CQ-BACKEND-22
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01483
Source document: source document page 23
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-BACKEND-24

Priority: P3
Baseline question ID: CQ-BACKEND-23
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01576
Source document: source document page 30
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-LOG-01

Priority: P3
Baseline question ID: CQ-LOG-01
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01268
Source document: source document page 18
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-OPS-01

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00087
Source document: source document page 8
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-EVIDENCE-01

Priority: P3
Baseline question ID: Not in pre-additional baseline
Previous status: Not in pre-additional baseline
Source of question: Introduced by additional PDFs
Original 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.
New status: Introduced by Additional PDF
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00223
Source document: source document page 29
Closure decision: Introduced by Additional PDF
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-EVIDENCE-02

Priority: P3
Baseline question ID: CQ-EVIDENCE-01
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00588
Source document: source document page 25
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-EVIDENCE-03

Priority: P3
Baseline question ID: CQ-EVIDENCE-02
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00677
Source document: source document page 38
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-EVIDENCE-04

Priority: P3
Baseline question ID: CQ-EVIDENCE-03
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-00690
Source document: source document page 40
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-EVIDENCE-05

Priority: P3
Baseline question ID: CQ-EVIDENCE-04
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01292
Source document: source document page 4
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-EVIDENCE-06

Priority: P3
Baseline question ID: CQ-EVIDENCE-05
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01305
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-EVIDENCE-07

Priority: P3
Baseline question ID: CQ-EVIDENCE-06
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01306
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes

CQ-EVIDENCE-08

Priority: P3
Baseline question ID: CQ-EVIDENCE-07
Previous status: Reclassified as Informational
Source of question: Pre-additional baseline
Original 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.
New status: Open
Evidence from additional PDF: None
Related Related requirements: REQ-AUTO-01310
Source document: source document page 6
Closure decision: Open
Confidence level: Low
Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
Customer confirmation still needed: yes