Customer Workshop

Workshop Execution Pack

Customer Clarification Workshop Execution Pack

Workshop Objective

Run a structured clarification workshop that confirms or rejects RFQX assumptions, closes product/security architecture uncertainties, and captures customer decisions without converting unanswered questions into requirements.

Required Participants

• OEM product owner
• OEM system architect
• OEM cybersecurity architect
• OEM diagnostic expert
• OEM backend/cloud owner
• OEM PKI/key management owner
• Supplier system architect
• Supplier cybersecurity engineer
• Supplier software architect
• Supplier hardware/platform owner
• Tooling/ALM owner
• TARA/residual-risk approver

Pre-Read Material

• site/index.html
• site/product-understanding.html
• site/interfaces.html
• site/cybersecurity.html
• site/architecture.html
• site/open-decisions.html
• customer_review/source document
• customer_review/source document

Meeting Structure

• Clarification questions: 472 total; P1=6, P2=1, P3=465.
• Block 1: Product and Boundary.
• Block 2: Interfaces and Data Flows.
• Block 3: Security Concept and Assets.
• Block 4: Diagnostics / Update / PKI.
• Block 5: Ownership and Operations.
• Block 6: TARA / Residual Risk.

Product Understanding Review

Confirm product identity, vehicle/ECU context, operational need, and what the requirements do not prove.

System Boundary Review

Confirm item boundary, adjacent ECUs, customer/OEM systems, supplier responsibilities, and assumed deployment zones.

Interface Review

Confirm external/internal interfaces, protocols, data exchanged, owner, trust-boundary crossing, and required protection.

Security Concept Review

Confirm assets, attack surfaces, security goals, expected controls, lifecycle responsibilities, and ownership of PKI, diagnostics, update, logging, monitoring, and incident response.

Architecture Review

Walk through context, logical architecture, cybersecurity architecture, trust boundaries, data flows, and unresolved assumptions as tracked review items.

Decision Capture Rules

• Do not treat unanswered clarification questions as confirmed requirements.
• Do not convert assumptions into explicit requirements unless a customer answer supports it.
• Every customer answer must reference a Question ID.
• Every decision must include owner, status, affected baseline areas, and evidence or meeting reference.
• Every post-workshop baseline update must show before state, after state, delta impact, and remaining open points.

Expected Outputs

• Completed customer answer capture sheet.
• Decision log with owner and status for each answered item.
• New questions created during the workshop.
• Agreement on which assumptions remain tracked and which baseline areas require update.

Post-Workshop Update Process

1. Save customer answers under configured customer input folder. 2. Run python scripts/ingest_customer_answers.py. 3. Run python scripts/update_baseline_from_customer_answers.py. 4. Re-run synthesis, site generation, validation, and evidence export. 5. Review post-workshop deltas before claiming any customer-approved baseline state.

Clarification Priority Matrix

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

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

Questions by Domain

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

Questions by Owner

• Joint: 464
• Supplier: 8

Questions by Impacted Architecture Area

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

Sequenced Question Register

CQ-BOUNDARY-03

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

CQ-BOUNDARY-05

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

CQ-BOUNDARY-127

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

CQ-BOUNDARY-158

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

CQ-BOUNDARY-199

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

CQ-BOUNDARY-201

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

CQ-BACKEND-02

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

CQ-BOUNDARY-01

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

CQ-BOUNDARY-02

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

CQ-BOUNDARY-04

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

CQ-BOUNDARY-06

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

CQ-BOUNDARY-07

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

CQ-BOUNDARY-08

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

CQ-BOUNDARY-09

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

CQ-BOUNDARY-10

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

CQ-BOUNDARY-100

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

CQ-BOUNDARY-101

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

CQ-BOUNDARY-102

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

CQ-BOUNDARY-103

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

CQ-BOUNDARY-104

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

CQ-BOUNDARY-105

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

CQ-BOUNDARY-106

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

CQ-BOUNDARY-107

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

CQ-BOUNDARY-108

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

CQ-BOUNDARY-109

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

CQ-BOUNDARY-11

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

CQ-BOUNDARY-110

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

CQ-BOUNDARY-111

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

CQ-BOUNDARY-112

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

CQ-BOUNDARY-113

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

CQ-BOUNDARY-114

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

CQ-BOUNDARY-115

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

CQ-BOUNDARY-116

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

CQ-BOUNDARY-117

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

CQ-BOUNDARY-118

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

CQ-BOUNDARY-119

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

CQ-BOUNDARY-12

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

CQ-BOUNDARY-120

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

CQ-BOUNDARY-121

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

CQ-BOUNDARY-122

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

CQ-BOUNDARY-123

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

CQ-BOUNDARY-124

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

CQ-BOUNDARY-125

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

CQ-BOUNDARY-126

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

CQ-BOUNDARY-128

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

CQ-BOUNDARY-129

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

CQ-BOUNDARY-13

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

CQ-BOUNDARY-130

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

CQ-BOUNDARY-131

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

CQ-BOUNDARY-132

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

CQ-BOUNDARY-133

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

CQ-BOUNDARY-134

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

CQ-BOUNDARY-135

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

CQ-BOUNDARY-136

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

CQ-BOUNDARY-137

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

CQ-BOUNDARY-138

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

CQ-BOUNDARY-139

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

CQ-BOUNDARY-14

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

CQ-BOUNDARY-140

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

CQ-BOUNDARY-141

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

CQ-BOUNDARY-142

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

CQ-BOUNDARY-143

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

CQ-BOUNDARY-144

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

CQ-BOUNDARY-145

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

CQ-BOUNDARY-146

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

CQ-BOUNDARY-147

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

CQ-BOUNDARY-148

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

CQ-BOUNDARY-149

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

CQ-BOUNDARY-15

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

CQ-BOUNDARY-150

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

CQ-BOUNDARY-151

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

CQ-BOUNDARY-152

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

CQ-BOUNDARY-153

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

CQ-BOUNDARY-154

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

CQ-BOUNDARY-155

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

CQ-BOUNDARY-156

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

CQ-BOUNDARY-157

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

CQ-BOUNDARY-159

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

CQ-BOUNDARY-16

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

CQ-BOUNDARY-160

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

CQ-BOUNDARY-161

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

CQ-BOUNDARY-162

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

CQ-BOUNDARY-163

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

CQ-BOUNDARY-164

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

CQ-BOUNDARY-165

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

CQ-BOUNDARY-166

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

CQ-BOUNDARY-167

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

CQ-BOUNDARY-168

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

CQ-BOUNDARY-169

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

CQ-BOUNDARY-17

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

CQ-BOUNDARY-170

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

CQ-BOUNDARY-171

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

CQ-BOUNDARY-172

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

CQ-BOUNDARY-173

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

CQ-BOUNDARY-174

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

CQ-BOUNDARY-175

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

CQ-BOUNDARY-176

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

CQ-BOUNDARY-177

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

CQ-BOUNDARY-178

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

CQ-BOUNDARY-179

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

CQ-BOUNDARY-18

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

CQ-BOUNDARY-180

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

CQ-BOUNDARY-181

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

CQ-BOUNDARY-182

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

CQ-BOUNDARY-183

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

CQ-BOUNDARY-184

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

CQ-BOUNDARY-185

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

CQ-BOUNDARY-186

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

CQ-BOUNDARY-187

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

CQ-BOUNDARY-188

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

CQ-BOUNDARY-189

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

CQ-BOUNDARY-19

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

CQ-BOUNDARY-190

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

CQ-BOUNDARY-191

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

CQ-BOUNDARY-192

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

CQ-BOUNDARY-193

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

CQ-BOUNDARY-194

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

CQ-BOUNDARY-195

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

CQ-BOUNDARY-196

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

CQ-BOUNDARY-197

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

CQ-BOUNDARY-198

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

CQ-BOUNDARY-20

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

CQ-BOUNDARY-200

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

CQ-BOUNDARY-202

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

CQ-BOUNDARY-203

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

CQ-BOUNDARY-204

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

CQ-BOUNDARY-205

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

CQ-BOUNDARY-206

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

CQ-BOUNDARY-207

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

CQ-BOUNDARY-208

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

CQ-BOUNDARY-209

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

CQ-BOUNDARY-21

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

CQ-BOUNDARY-210

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

CQ-BOUNDARY-211

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

CQ-BOUNDARY-212

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

CQ-BOUNDARY-213

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

CQ-BOUNDARY-214

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

CQ-BOUNDARY-215

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

CQ-BOUNDARY-216

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

CQ-BOUNDARY-217

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

CQ-BOUNDARY-218

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

CQ-BOUNDARY-219

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

CQ-BOUNDARY-22

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

CQ-BOUNDARY-220

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

CQ-BOUNDARY-221

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

CQ-BOUNDARY-222

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

CQ-BOUNDARY-223

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

CQ-BOUNDARY-224

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

CQ-BOUNDARY-225

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

CQ-BOUNDARY-226

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

CQ-BOUNDARY-227

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

CQ-BOUNDARY-228

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

CQ-BOUNDARY-229

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

CQ-BOUNDARY-23

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

CQ-BOUNDARY-230

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

CQ-BOUNDARY-231

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

CQ-BOUNDARY-232

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

CQ-BOUNDARY-233

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

CQ-BOUNDARY-234

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

CQ-BOUNDARY-235

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

CQ-BOUNDARY-236

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

CQ-BOUNDARY-237

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

CQ-BOUNDARY-238

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

CQ-BOUNDARY-239

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

CQ-BOUNDARY-24

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

CQ-BOUNDARY-240

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

CQ-BOUNDARY-241

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

CQ-BOUNDARY-242

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

CQ-BOUNDARY-243

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

CQ-BOUNDARY-244

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

CQ-BOUNDARY-25

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

CQ-BOUNDARY-26

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

CQ-BOUNDARY-27

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

CQ-BOUNDARY-28

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

CQ-BOUNDARY-29

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

CQ-BOUNDARY-30

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

CQ-BOUNDARY-31

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

CQ-BOUNDARY-32

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

CQ-BOUNDARY-33

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

CQ-BOUNDARY-34

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

CQ-BOUNDARY-35

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

CQ-BOUNDARY-36

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

CQ-BOUNDARY-37

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

CQ-BOUNDARY-38

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

CQ-BOUNDARY-39

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

CQ-BOUNDARY-40

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

CQ-BOUNDARY-41

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

CQ-BOUNDARY-42

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

CQ-BOUNDARY-43

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

CQ-BOUNDARY-44

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

CQ-BOUNDARY-45

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

CQ-BOUNDARY-46

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

CQ-BOUNDARY-47

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

CQ-BOUNDARY-48

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

CQ-BOUNDARY-49

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

CQ-BOUNDARY-50

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

CQ-BOUNDARY-51

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

CQ-BOUNDARY-52

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

CQ-BOUNDARY-53

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

CQ-BOUNDARY-54

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

CQ-BOUNDARY-55

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

CQ-BOUNDARY-56

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

CQ-BOUNDARY-57

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

CQ-BOUNDARY-58

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

CQ-BOUNDARY-59

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

CQ-BOUNDARY-60

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

CQ-BOUNDARY-61

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

CQ-BOUNDARY-62

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

CQ-BOUNDARY-63

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

CQ-BOUNDARY-64

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

CQ-BOUNDARY-65

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

CQ-BOUNDARY-66

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

CQ-BOUNDARY-67

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

CQ-BOUNDARY-68

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

CQ-BOUNDARY-69

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

CQ-BOUNDARY-70

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

CQ-BOUNDARY-71

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

CQ-BOUNDARY-72

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

CQ-BOUNDARY-73

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

CQ-BOUNDARY-74

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

CQ-BOUNDARY-75

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

CQ-BOUNDARY-76

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

CQ-BOUNDARY-77

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

CQ-BOUNDARY-78

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

CQ-BOUNDARY-79

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

CQ-BOUNDARY-80

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

CQ-BOUNDARY-81

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

CQ-BOUNDARY-82

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

CQ-BOUNDARY-83

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

CQ-BOUNDARY-84

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

CQ-BOUNDARY-85

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

CQ-BOUNDARY-86

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

CQ-BOUNDARY-87

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

CQ-BOUNDARY-88

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

CQ-BOUNDARY-89

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

CQ-BOUNDARY-90

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

CQ-BOUNDARY-91

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

CQ-BOUNDARY-92

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

CQ-BOUNDARY-93

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

CQ-BOUNDARY-94

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

CQ-BOUNDARY-95

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

CQ-BOUNDARY-96

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

CQ-BOUNDARY-97

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

CQ-BOUNDARY-98

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

CQ-BOUNDARY-99

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

CQ-INTERFACE-01

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

CQ-INTERFACE-02

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

CQ-INTERFACE-03

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

CQ-INTERFACE-04

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

CQ-INTERFACE-05

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

CQ-INTERFACE-06

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

CQ-INTERFACE-07

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

CQ-INTERFACE-08

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

CQ-INTERFACE-09

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

CQ-INTERFACE-10

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

CQ-INTERFACE-11

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

CQ-INTERFACE-12

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

CQ-INTERFACE-13

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

CQ-INTERFACE-14

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

CQ-INTERFACE-15

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

CQ-INTERFACE-16

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

CQ-INTERFACE-17

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

CQ-INTERFACE-18

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

CQ-INTERFACE-19

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

CQ-INTERFACE-20

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

CQ-INTERFACE-21

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

CQ-INTERFACE-22

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

CQ-INTERFACE-23

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

CQ-INTERFACE-24

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

CQ-INTERFACE-25

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

CQ-INTERFACE-26

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

CQ-INTERFACE-27

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

CQ-INTERFACE-28

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

CQ-INTERFACE-29

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

CQ-INTERFACE-30

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

CQ-INTERFACE-31

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

CQ-INTERFACE-32

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

CQ-INTERFACE-33

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

CQ-INTERFACE-34

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

CQ-INTERFACE-35

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

CQ-INTERFACE-36

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

CQ-INTERFACE-37

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

CQ-INTERFACE-38

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

CQ-INTERFACE-39

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

CQ-INTERFACE-40

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

CQ-INTERFACE-41

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

CQ-INTERFACE-42

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

CQ-INTERFACE-43

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

CQ-INTERFACE-44

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

CQ-INTERFACE-45

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

CQ-INTERFACE-46

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

CQ-INTERFACE-47

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

CQ-INTERFACE-48

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

CQ-INTERFACE-49

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

CQ-INTERFACE-50

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

CQ-INTERFACE-51

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

CQ-INTERFACE-52

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

CQ-INTERFACE-53

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

CQ-INTERFACE-54

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

CQ-INTERFACE-55

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

CQ-INTERFACE-56

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

CQ-INTERFACE-57

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

CQ-INTERFACE-58

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

CQ-INTERFACE-59

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

CQ-INTERFACE-60

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

CQ-INTERFACE-61

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

CQ-INTERFACE-62

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

CQ-INTERFACE-63

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

CQ-INTERFACE-64

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

CQ-INTERFACE-65

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

CQ-INTERFACE-66

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

CQ-INTERFACE-67

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

CQ-INTERFACE-68

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

CQ-INTERFACE-69

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

CQ-HSM-01

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

CQ-HSM-02

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

CQ-HSM-03

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

CQ-HSM-04

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

CQ-HSM-05

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

CQ-HSM-06

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

CQ-HSM-07

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

CQ-HSM-08

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

CQ-LOG-01

• Priority: P3
• Workshop Block: Block 3: Security Concept and Assets
• Decision Type: Security Concept
• Domain: Logging and Monitoring
• Recommended owner: Joint
• Impacted architecture/security area: Logging and Audit / Security Monitoring
• Related Related requirements: RFQX-CVS151-0076

CQ-DIAG-01

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS123-2-0013

CQ-DIAG-02

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS123-2-0026

CQ-DIAG-03

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS123-2-0088

CQ-DIAG-04

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS123-2-0092

CQ-DIAG-05

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS123-2-0097

CQ-DIAG-06

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS123-2-0105

CQ-DIAG-07

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS123-2-0123

CQ-DIAG-08

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS123-2-0124

CQ-DIAG-09

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS123-2-0126

CQ-DIAG-10

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS123-2-0128

CQ-DIAG-11

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS123-2-0136

CQ-DIAG-12

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS123-2-0159

CQ-DIAG-13

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS123-2-0231

CQ-DIAG-14

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS123-2-0290

CQ-DIAG-15

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0022

CQ-DIAG-16

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0026

CQ-DIAG-17

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0035

CQ-DIAG-18

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0047

CQ-DIAG-19

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0052

CQ-DIAG-20

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0090

CQ-DIAG-21

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0091

CQ-DIAG-22

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0095

CQ-DIAG-23

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0096

CQ-DIAG-24

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0097

CQ-DIAG-25

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0099

CQ-DIAG-26

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0100

CQ-DIAG-27

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0101

CQ-DIAG-28

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0103

CQ-DIAG-29

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0106

CQ-DIAG-30

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0107

CQ-DIAG-31

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0108

CQ-DIAG-32

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0110

CQ-DIAG-33

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0112

CQ-DIAG-34

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0113

CQ-DIAG-35

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0114

CQ-DIAG-36

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0116

CQ-DIAG-37

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0136

CQ-DIAG-38

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0170

CQ-DIAG-39

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0188

CQ-DIAG-40

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0189

CQ-DIAG-41

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0190

CQ-DIAG-42

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0191

CQ-DIAG-43

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0200

CQ-DIAG-44

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0208

CQ-DIAG-45

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0211

CQ-DIAG-46

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0214

CQ-DIAG-47

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0218

CQ-DIAG-48

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0231

CQ-DIAG-49

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0261

CQ-DIAG-50

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0262

CQ-DIAG-51

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0271

CQ-DIAG-52

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0286

CQ-DIAG-53

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0293

CQ-DIAG-54

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0342

CQ-DIAG-55

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0358

CQ-DIAG-56

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0359

CQ-DIAG-57

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0360

CQ-DIAG-58

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0363

CQ-DIAG-59

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0394

CQ-DIAG-60

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0395

CQ-DIAG-61

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0401

CQ-DIAG-62

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0411

CQ-DIAG-63

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0413

CQ-DIAG-64

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0422

CQ-DIAG-65

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0423

CQ-DIAG-66

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0424

CQ-DIAG-67

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0425

CQ-DIAG-68

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0426

CQ-DIAG-69

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0428

CQ-DIAG-70

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0429

CQ-DIAG-71

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0430

CQ-DIAG-72

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0451

CQ-DIAG-73

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0452

CQ-DIAG-74

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0454

CQ-DIAG-75

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0455

CQ-DIAG-76

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0456

CQ-DIAG-77

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0460

CQ-DIAG-78

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0461

CQ-DIAG-79

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS124-0465

CQ-DIAG-80

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS151-0067

CQ-DIAG-81

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS151-0077

CQ-DIAG-82

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS31-0018

CQ-DIAG-83

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS31-0044

CQ-DIAG-84

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS31-0076

CQ-DIAG-85

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS31-0116

CQ-DIAG-86

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS31-0118

CQ-DIAG-87

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS31-0129

CQ-DIAG-88

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS31-0130

CQ-DIAG-89

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS31-0144

CQ-DIAG-90

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS31-0145

CQ-DIAG-91

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS31-0159

CQ-DIAG-92

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS31-0161

CQ-DIAG-93

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS31-0249

CQ-DIAG-94

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Interface
• Domain: Diagnostic and Service Access
• Recommended owner: Joint
• Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
• Related Related requirements: RFQX-CVS32-0017

CQ-PKI-01

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: PKI, Keys, Certificates
• Recommended owner: Joint
• Impacted architecture/security area: Key and Certificate Management
• Related Related requirements: RFQX-CVS123-2-0296

CQ-PKI-02

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: PKI, Keys, Certificates
• Recommended owner: Joint
• Impacted architecture/security area: Key and Certificate Management
• Related Related requirements: RFQX-CVS31-0034

CQ-PKI-03

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: PKI, Keys, Certificates
• Recommended owner: Joint
• Impacted architecture/security area: Key and Certificate Management
• Related Related requirements: RFQX-CVS31-0055

CQ-PKI-04

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: PKI, Keys, Certificates
• Recommended owner: Joint
• Impacted architecture/security area: Key and Certificate Management
• Related Related requirements: RFQX-CVS31-0057

CQ-PKI-05

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: PKI, Keys, Certificates
• Recommended owner: Joint
• Impacted architecture/security area: Key and Certificate Management
• Related Related requirements: RFQX-CVS31-0127

CQ-PKI-06

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: PKI, Keys, Certificates
• Recommended owner: Joint
• Impacted architecture/security area: Key and Certificate Management
• Related Related requirements: RFQX-CVS31-0164

CQ-PKI-07

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: PKI, Keys, Certificates
• Recommended owner: Joint
• Impacted architecture/security area: Key and Certificate Management
• Related Related requirements: RFQX-CVS31-0197

CQ-PKI-08

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: PKI, Keys, Certificates
• Recommended owner: Joint
• Impacted architecture/security area: Key and Certificate Management
• Related Related requirements: RFQX-CVS31-0211

CQ-PKI-09

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: PKI, Keys, Certificates
• Recommended owner: Joint
• Impacted architecture/security area: Key and Certificate Management
• Related Related requirements: RFQX-CVS31-0246

CQ-UPDATE-01

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: Software Update / IVD
• Recommended owner: Joint
• Impacted architecture/security area: Secure update / IVD architecture
• Related Related requirements: RFQX-CVS123-2-0004

CQ-UPDATE-02

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: Software Update / IVD
• Recommended owner: Joint
• Impacted architecture/security area: Secure update / IVD architecture
• Related Related requirements: RFQX-CVS123-2-0076

CQ-UPDATE-03

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: Software Update / IVD
• Recommended owner: Joint
• Impacted architecture/security area: Secure update / IVD architecture
• Related Related requirements: RFQX-CVS123-2-0077

CQ-UPDATE-04

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: Software Update / IVD
• Recommended owner: Joint
• Impacted architecture/security area: Secure update / IVD architecture
• Related Related requirements: RFQX-CVS123-2-0083

CQ-UPDATE-05

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: Software Update / IVD
• Recommended owner: Joint
• Impacted architecture/security area: Secure update / IVD architecture
• Related Related requirements: RFQX-CVS123-2-0095

CQ-UPDATE-06

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: Software Update / IVD
• Recommended owner: Joint
• Impacted architecture/security area: Secure update / IVD architecture
• Related Related requirements: RFQX-CVS123-2-0109

CQ-UPDATE-07

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: Software Update / IVD
• Recommended owner: Joint
• Impacted architecture/security area: Secure update / IVD architecture
• Related Related requirements: RFQX-CVS123-2-0119

CQ-UPDATE-08

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: Software Update / IVD
• Recommended owner: Joint
• Impacted architecture/security area: Secure update / IVD architecture
• Related Related requirements: RFQX-CVS123-2-0120

CQ-UPDATE-09

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: Software Update / IVD
• Recommended owner: Joint
• Impacted architecture/security area: Secure update / IVD architecture
• Related Related requirements: RFQX-CVS123-2-0121

CQ-UPDATE-10

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: Software Update / IVD
• Recommended owner: Joint
• Impacted architecture/security area: Secure update / IVD architecture
• Related Related requirements: RFQX-CVS123-2-0134

CQ-UPDATE-11

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: Software Update / IVD
• Recommended owner: Joint
• Impacted architecture/security area: Secure update / IVD architecture
• Related Related requirements: RFQX-CVS123-2-0135

CQ-UPDATE-12

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: Software Update / IVD
• Recommended owner: Joint
• Impacted architecture/security area: Secure update / IVD architecture
• Related Related requirements: RFQX-CVS123-2-0163

CQ-UPDATE-13

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: Software Update / IVD
• Recommended owner: Joint
• Impacted architecture/security area: Secure update / IVD architecture
• Related Related requirements: RFQX-CVS123-2-0170

CQ-UPDATE-14

• Priority: P3
• Workshop Block: Block 4: Diagnostics / Update / PKI
• Decision Type: Security Concept
• Domain: Software Update / IVD
• Recommended owner: Joint
• Impacted architecture/security area: Secure update / IVD architecture
• Related Related requirements: RFQX-CVS123-2-0270

CQ-BACKEND-01

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Ownership
• Domain: Backend / SecOps Ownership
• Recommended owner: Joint
• Impacted architecture/security area: Backend and IT Systems / Security Operations
• Related Related requirements: RFQX-3299216-1-0226

CQ-BACKEND-03

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

CQ-BACKEND-04

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

CQ-BACKEND-05

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

CQ-BACKEND-06

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

CQ-BACKEND-07

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

CQ-BACKEND-08

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

CQ-BACKEND-09

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

CQ-BACKEND-10

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

CQ-BACKEND-11

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

CQ-BACKEND-12

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

CQ-BACKEND-13

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Ownership
• Domain: Backend / SecOps Ownership
• Recommended owner: Joint
• Impacted architecture/security area: Backend and IT Systems / Security Operations
• Related Related requirements: RFQX-CVS151-0017

CQ-BACKEND-14

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Ownership
• Domain: Backend / SecOps Ownership
• Recommended owner: Joint
• Impacted architecture/security area: Backend and IT Systems / Security Operations
• Related Related requirements: RFQX-CVS151-0024

CQ-BACKEND-15

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Ownership
• Domain: Backend / SecOps Ownership
• Recommended owner: Joint
• Impacted architecture/security area: Backend and IT Systems / Security Operations
• Related Related requirements: RFQX-CVS151-0026

CQ-BACKEND-16

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Ownership
• Domain: Backend / SecOps Ownership
• Recommended owner: Joint
• Impacted architecture/security area: Backend and IT Systems / Security Operations
• Related Related requirements: RFQX-CVS154-0022

CQ-BACKEND-17

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Ownership
• Domain: Backend / SecOps Ownership
• Recommended owner: Joint
• Impacted architecture/security area: Backend and IT Systems / Security Operations
• Related Related requirements: RFQX-CVS154-0023

CQ-BACKEND-18

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Ownership
• Domain: Backend / SecOps Ownership
• Recommended owner: Joint
• Impacted architecture/security area: Backend and IT Systems / Security Operations
• Related Related requirements: RFQX-CVS31-0082

CQ-BACKEND-19

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Ownership
• Domain: Backend / SecOps Ownership
• Recommended owner: Joint
• Impacted architecture/security area: Backend and IT Systems / Security Operations
• Related Related requirements: RFQX-CVS31-0091

CQ-BACKEND-20

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Ownership
• Domain: Backend / SecOps Ownership
• Recommended owner: Joint
• Impacted architecture/security area: Backend and IT Systems / Security Operations
• Related Related requirements: RFQX-CVS31-0097

CQ-BACKEND-21

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Ownership
• Domain: Backend / SecOps Ownership
• Recommended owner: Joint
• Impacted architecture/security area: Backend and IT Systems / Security Operations
• Related Related requirements: RFQX-CVS31-0108

CQ-BACKEND-22

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Ownership
• Domain: Backend / SecOps Ownership
• Recommended owner: Joint
• Impacted architecture/security area: Backend and IT Systems / Security Operations
• Related Related requirements: RFQX-CVS31-0149

CQ-BACKEND-23

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Ownership
• Domain: Backend / SecOps Ownership
• Recommended owner: Joint
• Impacted architecture/security area: Backend and IT Systems / Security Operations
• Related Related requirements: RFQX-CVS31-0150

CQ-BACKEND-24

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Ownership
• Domain: Backend / SecOps Ownership
• Recommended owner: Joint
• Impacted architecture/security area: Backend and IT Systems / Security Operations
• Related Related requirements: RFQX-CVS31-0243

CQ-OPS-01

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Ownership
• Domain: Operational Responsibilities
• Recommended owner: Joint
• Impacted architecture/security area: Operational and Lifecycle Capabilities
• Related Related requirements: RFQX-3299216-1-0020

CQ-EVIDENCE-01

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Tooling / Evidence
• Domain: Tooling / Evidence / Compliance
• Recommended owner: Joint
• Impacted architecture/security area: Engineering Toolchain / Compliance Process
• Related Related requirements: RFQX-3299216-1-0156

CQ-EVIDENCE-02

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Tooling / Evidence
• Domain: Tooling / Evidence / Compliance
• Recommended owner: Joint
• Impacted architecture/security area: Engineering Toolchain / Compliance Process
• Related Related requirements: RFQX-CVS123-2-0212

CQ-EVIDENCE-03

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Tooling / Evidence
• Domain: Tooling / Evidence / Compliance
• Recommended owner: Joint
• Impacted architecture/security area: Engineering Toolchain / Compliance Process
• Related Related requirements: RFQX-CVS123-2-0301

CQ-EVIDENCE-04

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Tooling / Evidence
• Domain: Tooling / Evidence / Compliance
• Recommended owner: Joint
• Impacted architecture/security area: Engineering Toolchain / Compliance Process
• Related Related requirements: RFQX-CVS123-2-0314

CQ-EVIDENCE-05

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Tooling / Evidence
• Domain: Tooling / Evidence / Compliance
• Recommended owner: Joint
• Impacted architecture/security area: Engineering Toolchain / Compliance Process
• Related Related requirements: RFQX-CVS154-0006

CQ-EVIDENCE-06

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Tooling / Evidence
• Domain: Tooling / Evidence / Compliance
• Recommended owner: Joint
• Impacted architecture/security area: Engineering Toolchain / Compliance Process
• Related Related requirements: RFQX-CVS154-0019

CQ-EVIDENCE-07

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Tooling / Evidence
• Domain: Tooling / Evidence / Compliance
• Recommended owner: Joint
• Impacted architecture/security area: Engineering Toolchain / Compliance Process
• Related Related requirements: RFQX-CVS154-0020

CQ-EVIDENCE-08

• Priority: P3
• Workshop Block: Block 5: Ownership and Operations
• Decision Type: Tooling / Evidence
• Domain: Tooling / Evidence / Compliance
• Recommended owner: Joint
• Impacted architecture/security area: Engineering Toolchain / Compliance Process
• Related Related requirements: RFQX-CVS154-0024

Questions Grouped by Workshop Block

Customer Clarification Questions

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

Total clarification questions: 472

Product/System Boundary

CQ-BOUNDARY-03

• Question: Confirm the customer decision needed to baseline this requirement item: Term Definition Shall This word, or the term "Required", means that the definition is an absolute requirement of the specification. Threat Analysis and Risk Assessment A structured approach to identify possible threats and evaluate risks with respect to the potential damages and the effort needed for successful attack. Cybersecurity concept A cybersecurity concept is a work product that documents cybersecurity relevant aspects of the product. The cybersecurity concept shall describe the scope of the risk analysis, risks that were identified during the risk analysis, cybe rsecurity goals, cybersecurity requirements, mitigation strategies, validation, and verification strategies, etc. Table 1: Definition of terms. This affects product/system boundary scope, supplier positioning, and traceability status.
• Priority: P1
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Blocks architecture baseline
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-1001379436-P10-000-01-0003
• Source document: source document page 3
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Not Applicable
• Rationale: Requirement was not low-confidence in the extracted baseline.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-05

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

CQ-BOUNDARY-127

• Question: Confirm the customer decision needed to baseline this requirement item: Table 1 – Definition of Terms Term Definition Shall This word, or the terms "Required" or "Must", means that the definition is an absolute requirement of the specification. Shall not This phrase, or the phrase "Must not", means that the definition is an absolute prohibition of the specification. Should This word, or the adjective “Recommended”, means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications shall be understood and carefully weighed before choosing a different course. Should not This phrase, or the phrase “Not recommended”, means that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. May This word, or the adjective “Optional”, means that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation which does not include a particular option shall be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option shall be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides).. This affects product/system boundary scope, supplier positioning, and traceability status.
• Priority: P1
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Blocks architecture baseline
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS124-0005
• Source document: source document page 6
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Not Applicable
• Rationale: Requirement was not low-confidence in the extracted baseline.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-158

• Question: Confirm the customer decision needed to baseline this requirement item: Byte Description Range Resolu tion This byte shall be set to value 2 and is used to identify the response structure variant #9 Occurrence counter OCC, as described in section 5.7.2 [unsigned integer] 0..127 0 M #10 DTC priority 1 – Highest priority 2 - Second highest priority 3 – Lowest priority 255 – Unknown 1..3, 255 0xFF M #11..#16 Time/Date of the first DTC activation See Table 98 but without byte #7 and #8 M #17..#22 Time/Date of the latest DTC activation M #23..#26 ECU Operational hours at the first DTC activation [4-byte int, big endian] as described in section 5.7.5.2.. This affects product/system boundary scope, supplier positioning, and traceability status.
• Priority: P1
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Blocks architecture baseline
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS124-0246
• Source document: source document page 52
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Not Applicable
• Rationale: Requirement was not low-confidence in the extracted baseline.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-199

• Question: Confirm the customer decision needed to baseline this requirement item: The server shall have support for the ASN.1 contents as defined: DataSecurityContainer ::= SEQUENCE { version OCTET STRING (SIZE(2)), id OCTET STRING (SIZE(16)), verificationEntries SEQUENCE (SIZE(0..MAX)) OF VerificationEntry, encryptionEntries SEQUENCE (SIZE(0..MAX)) OF EncryptionEntry, itemEntries SEQUENCE (SIZE(0..MAX)) OF ItemEntry } VerificationEntry ::= CHOICE { hashCmp [0] EXPLICIT HashCmp }. This affects product/system boundary scope, supplier positioning, and traceability status.
• Priority: P1
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Blocks architecture baseline
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS154-0035
• Source document: source document page 9
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Not Applicable
• Rationale: Requirement was not low-confidence in the extracted baseline.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-201

• Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The purpose of this document is to clarify vehicle manufacture specific extensions and exceptions to the Authentication 0x29 service specified in ISO 14229-1:2020. CVS150 Cryptographic Specification CVS32 SecuredDataTransmis sion 0x84 CVS151 RBAC CVS33 Entity Management Protocol (EMP) CVS31 Authenticate 0x29 CVS124 Traton Specification on Unified diagnostic services (UDS) CVS30 X.509 Specification CVS34 EMP – Basic Entities Figure 1 – Overview of relation between specifications The following documents are normative and indispensable for the application of this document: • Traton Specification on Unified diagnostic Services (UDS) requirements (CVS124) • ISO 14229-1:2020, Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements Whenever a requirement in this specification or the Traton Specification on Unified diagnostic Services (UDS) requirements (CVS124) is non-compliant with one or more requirements in ISO 14229-1:2020 the requirements in this specification and (CVS124) take precedence. Any deviations from this specification shall be documented and must be reviewed by the vehicle manufacturer. It is the vehicle manufacturer that decides if a deviation can be accepted or not. Multiple security concepts are available in the Authentication (ISO 14229-1:2020) service, however, only APCE (ISO 14229-1:2020) is supported by the concept described in this document, see Figure 2.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
• Priority: P1
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Blocks architecture baseline
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS31-0006
• Source document: source document page 4
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Not Applicable
• Rationale: Requirement was not low-confidence in the extracted baseline.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-01

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

CQ-BOUNDARY-02

• Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The target readers of this specification are ECU suppliers, which can be either internal or external in relation to the vehicle manufacturer. In both cases, whenever the term “ECU supplier” or just “supplier” is used in this specification it refers to the company and organization which is responsible for the implementation and delivery of the ECU according to the requirements in this specification. And in both cases, whenever the term “vehicle manufacturer” is used in this specification this term refers to the system owner (responsible receiver) at the vehicle manufacturer.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-1001379436-P10-000-01-0002
• Source document: source document page 3
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-04

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

CQ-BOUNDARY-06

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

CQ-BOUNDARY-07

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

CQ-BOUNDARY-08

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

CQ-BOUNDARY-09

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

CQ-BOUNDARY-10

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

CQ-BOUNDARY-100

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

CQ-BOUNDARY-101

• Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: After the consistency check (independent of the result), the client initiates a server restart by posting a physically addressed ECUReset (0x11) (hardReset) service request with the SPRMIB not set.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS123-2-0147
• Source document: source document page 19
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-102

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

CQ-BOUNDARY-103

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

CQ-BOUNDARY-104

• Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Implementation hint: The boot manager checks the “application valid” flag (C1) to see if the ECU hardware/software is consistent and all software and data identification DIDs in CVS124 contain non-default values.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS123-2-0151
• Source document: source document page 20
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-105

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

CQ-BOUNDARY-106

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

CQ-BOUNDARY-107

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

CQ-BOUNDARY-108

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

CQ-BOUNDARY-109

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

CQ-BOUNDARY-11

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

CQ-BOUNDARY-110

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

CQ-BOUNDARY-111

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

CQ-BOUNDARY-112

• Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: This means, for example, that loss of application server specific diagnostic address, -bitrate or - system name as a result of a failure during boot parameter module programming in the workshop is not acceptable.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS123-2-0191
• Source document: source document page 22
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-113

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

CQ-BOUNDARY-114

• Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Implementation Hint: The following generator polynomial with the following initial value are suggested to be used for calculation of the checksum: G(X) = x32 + x26 + x23 + x22 + x16 + x12 + x11 + x10 + x8 + x7 + x5 + x4 + x2 + x + 1 Initial value: 0xFFFFFFFF 8.2.1 Request. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS123-2-0249
• Source document: source document page 31
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-115

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

CQ-BOUNDARY-116

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

CQ-BOUNDARY-117

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

CQ-BOUNDARY-118

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

CQ-BOUNDARY-119

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

CQ-BOUNDARY-12

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

CQ-BOUNDARY-120

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

CQ-BOUNDARY-121

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

CQ-BOUNDARY-122

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

CQ-BOUNDARY-123

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

CQ-BOUNDARY-124

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

CQ-BOUNDARY-125

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

CQ-BOUNDARY-126

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

CQ-BOUNDARY-128

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

CQ-BOUNDARY-129

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

CQ-BOUNDARY-13

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

CQ-BOUNDARY-130

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

CQ-BOUNDARY-131

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

CQ-BOUNDARY-132

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

CQ-BOUNDARY-133

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

CQ-BOUNDARY-134

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

CQ-BOUNDARY-135

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

CQ-BOUNDARY-136

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

CQ-BOUNDARY-137

• Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: . If the client posts a physical service request to change session from DefaultSession to ProgrammingSession in the application software, the server sends a negative response with NRC 0x7E (sub-functionNotSupportedInActiveSession). Applies to non-reprogrammable servers: If the client requests a change to the ProgrammingSession in the DefaultSession in the application software, the server. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS124-0098
• Source document: source document page 28
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-138

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

CQ-BOUNDARY-139

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

CQ-BOUNDARY-14

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

CQ-BOUNDARY-140

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

CQ-BOUNDARY-141

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

CQ-BOUNDARY-142

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

CQ-BOUNDARY-143

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

CQ-BOUNDARY-144

• Question: Confirm the binding diagnostic behavior and service authorization expected for this item: . If a server exchanges diagnostic messages with the client within the ExtendedSession and state terminal 15 ON, the following step is performed if there is a change to terminal 15 OFF and response in progress was finished: Return to DefaultSession after an already started response message has been completely sent to the client.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS124-0120
• Source document: source document page 30
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-145

• Question: Confirm the binding diagnostic behavior and service authorization expected for this item: . If there is a state change from terminal 15 ON to terminal 15 OFF while a server exchanges diagnostic messages with the client within the DefaultSession, the server stops the communications with the client after sending the complete response to the last request.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS124-0121
• Source document: source document page 30
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-146

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

CQ-BOUNDARY-147

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

CQ-BOUNDARY-148

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

CQ-BOUNDARY-149

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

CQ-BOUNDARY-15

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

CQ-BOUNDARY-150

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

CQ-BOUNDARY-151

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

CQ-BOUNDARY-152

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

CQ-BOUNDARY-153

• Question: Confirm the binding diagnostic behavior and service authorization expected for this item: After a final positive response has been sent for ECUReset the server is not allowed to respond to any diagnostic service requests (except ECU identification) until it has restarted and been re- initialized.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS124-0151
• Source document: source document page 33
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-154

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

CQ-BOUNDARY-155

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

CQ-BOUNDARY-156

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

CQ-BOUNDARY-157

• Question: Confirm the customer decision needed to baseline this requirement item: Range tion #54 ECU start-up and alive reasons Bits 0-3 (start-up reason): 0x0: Reserved 0x1: Primary wake-up (terminal 15 ON) 0x2: Secondary wake-up 0x3: Sub wake-up 1 0x4: Sub wake-up 2 0x5: Sub wake-up 3 0x6-0xE: Reserved 0xF: Not available Bits 4-7 (alive reason): 0x0: Reserved 0x1: Primary wake-up (terminal 15 ON) 0x2: Secondary wake-up 0x3: Sub wake-up 1 0x4: Sub wake-up 2 0x5: Sub wake-up 3 0x6: Stay alive 0x7-0xE: Reserved 0xF: Not available Note 1: While the reason for keeping the ECU alive may change during execution startup reason and alive reason are always identical at ECU startup.. This affects product/system boundary scope, supplier positioning, and traceability status.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS124-0240
• Source document: source document page 49
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Assumption
• Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-159

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

CQ-BOUNDARY-16

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

CQ-BOUNDARY-160

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

CQ-BOUNDARY-161

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

CQ-BOUNDARY-162

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

CQ-BOUNDARY-163

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

CQ-BOUNDARY-164

• Question: Confirm the binding diagnostic behavior and service authorization expected for this item: RBAC for diagnostics Foreword This Commercial Vehicle Standard (“CVS151”) contains requirement specifications for TRATON Group and may be referred to by any of its commercial vehicle Affiliates.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS151-0001
• Source document: source document page 1
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Assumption
• Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-165

• Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 3 Technical content 3.1 Overview Server/ECUClient/tester UDS Authorize OK/NOTOK UDS request Is the request allowed, based on the client's access rights i.e., compare the client's role/s against the RBACCOK/NOTOK Figure 1 – Overview Figure 1 shows a highlevel view of the RBAC concept.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS151-0005
• Source document: source document page 4
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-166

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

CQ-BOUNDARY-167

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

CQ-BOUNDARY-168

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

CQ-BOUNDARY-169

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

CQ-BOUNDARY-17

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

CQ-BOUNDARY-170

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

CQ-BOUNDARY-171

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

CQ-BOUNDARY-172

• Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Examples of rules within a single role and their expected behaviour: Example 1: A rule in the RBACC states that a role can execute ReadDataByIdentifier 0x22 (see ISO-14229-1:2020) with Confidentiality off.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS151-0021
• Source document: source document page 5
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-173

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

CQ-BOUNDARY-174

• Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Examples of two roles with overlapping rules and their expected behaviour: Example 5: The RBACC contains two roles with rules that states how the role can execute ReadDataByIdentifier 0x22 (see ISO-14229-1:2020).. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS151-0025
• Source document: source document page 6
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-175

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

CQ-BOUNDARY-176

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

CQ-BOUNDARY-177

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

CQ-BOUNDARY-178

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

CQ-BOUNDARY-179

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

CQ-BOUNDARY-18

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

CQ-BOUNDARY-180

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

CQ-BOUNDARY-181

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

CQ-BOUNDARY-182

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

CQ-BOUNDARY-183

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

CQ-BOUNDARY-184

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

CQ-BOUNDARY-185

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

CQ-BOUNDARY-186

• Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: 4 Start 0 == This rule is not applicable when the RID is being started 1 == This rule is applicable when the RID is being started 5 Stop 0 == This rule is not applicable when the RID is being stopped 1 == This rule is applicable when the RID is being stopped 6 Read-results 0 == This rule is not applicable when the RID results are being read 1 == This rule is applicable when the RID results are being read 7 N/A Reserved for future use 3.10 Extending the Role Based Access Control Configuration using a certificate It is possible to extend the rules (in the RBACC), by including an extension in the user’s/client’s certificate (when certificate-based authorization is being used).. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS151-0059
• Source document: source document page 11
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-187

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

CQ-BOUNDARY-188

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

CQ-BOUNDARY-189

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

CQ-BOUNDARY-19

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

CQ-BOUNDARY-190

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

CQ-BOUNDARY-191

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

CQ-BOUNDARY-192

• Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Refreshing the S3 timer (see CVS124), e.g., using TesterPresent (0x3E) (see CVS37), is always possible to do outside the secure channel and regardless of the settings in the RBACC role configuration.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS151-0090
• Source document: source document page 20
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-193

• Question: Confirm the customer decision needed to baseline this requirement item: Data Security Container base definition Foreword This Commercial Vehicle Standard (“CVS154”) contains requirement specifications for TRATON Group and may be referred to by any of its commercial vehicle Affiliates.. This affects product/system boundary scope, supplier positioning, and traceability status.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS154-0001
• Source document: source document page 1
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Assumption
• Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-194

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

CQ-BOUNDARY-195

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

CQ-BOUNDARY-196

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

CQ-BOUNDARY-197

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

CQ-BOUNDARY-198

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

CQ-BOUNDARY-20

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

CQ-BOUNDARY-200

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

CQ-BOUNDARY-202

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

CQ-BOUNDARY-203

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

CQ-BOUNDARY-204

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

CQ-BOUNDARY-205

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

CQ-BOUNDARY-206

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

CQ-BOUNDARY-207

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

CQ-BOUNDARY-208

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

CQ-BOUNDARY-209

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

CQ-BOUNDARY-21

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

CQ-BOUNDARY-210

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

CQ-BOUNDARY-211

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

CQ-BOUNDARY-212

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

CQ-BOUNDARY-213

• Question: Confirm the binding diagnostic behavior and service authorization expected for this item: While the ECU-Diagnostic Role extension specifies the roles assigned to a client, the D-RBACC extension may both grant additional permissions and restrict permissions beyond those derived from the client’s roles.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS31-0092
• Source document: source document page 18
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Assumption
• Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-214

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

CQ-BOUNDARY-215

• Question: Confirm the binding diagnostic behavior and service authorization expected for this item: If a request to reset (e.g service 0x11) is received over the service 0x84 (securedDataTransmission) it permits the server to respond before the sessionKey is locked/invalidated.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS31-0112
• Source document: source document page 20
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-216

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

CQ-BOUNDARY-217

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

CQ-BOUNDARY-218

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

CQ-BOUNDARY-219

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

CQ-BOUNDARY-22

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

CQ-BOUNDARY-220

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

CQ-BOUNDARY-221

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

CQ-BOUNDARY-222

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

CQ-BOUNDARY-223

• Question: Confirm the binding diagnostic behavior and service authorization expected for this item: ephemeralPublicKeyServer) ephemeralPublicKeyServer, ephemeralPrivateKeyServer:= Curve25519() sessionKey := X25519(ephemeralPrivateKeyServer, ephemeralPublicKeyClient) sessionKey := X25519(ephemeralPrivateKeyClient , ephemeralPublicKeyServer) ephemeralPublicKeyClient, ephemeralPrivateKeyClient := Curve25519() ProofOfOwnership(...) VerifyCertificate(...) Figure 4 – Overview Ephemeral Diffie-Hellman key-exchange 4.4 External usage of the sessionKey The sessionKey is used outside the Authentication (ISO 14229-1:2020) service and is run through a key derivation function defined in (CVS32) to derive a key that can be used for securedDataTransmission communication.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS31-0139
• Source document: source document page 22
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-224

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

CQ-BOUNDARY-225

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

CQ-BOUNDARY-226

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

CQ-BOUNDARY-227

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

CQ-BOUNDARY-228

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

CQ-BOUNDARY-229

• Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: 2025-08 CVS31 First edition 2025-05-30 RFQ 2517 Delivery Added authentication delay timer Added Authentication Completion timer Clarified negative responses cases for each subfunction. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS31-0254
• Source document: source document page 30
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-23

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

CQ-BOUNDARY-230

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

CQ-BOUNDARY-231

• Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The purpose of this document is to clarify vehicle manufacturer specific extensions and exceptions to the SecuredDataTransmission 0x84 service specified in ISO14229-1:2020 [1]. This specification does not include any redundant requirements of the normative and indispensable documents referenced below. It contains only clarifications of the requirements and recommendations in these documents together with exceptions and additional requirements that apply to this standard in relation to these documents. The following documents are normative and indispensable for the application of this document: • TRATON Specification on Unified diagnostic Services (UDS) requirements [8] • ISO 14229-1:2020, Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements [1]. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS32-0005
• Source document: source document page 4
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-232

• Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The target readers for this specification are ECU-suppliers and ECU-developers in reference to the server-side requirements, and diagnostic tool developers and back-end service providers regarding the client-side requirements. These “target readers” can be either internal or external in relation to the vehicle manufacturer.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS32-0006
• Source document: source document page 4
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-233

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

CQ-BOUNDARY-234

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

CQ-BOUNDARY-235

• Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: The supported CipherSchemes SDT_AEAD_CHACHA20_POLY1305 and SDT_POLY1305 [9] are described in sections 3.2.2 and 3.2.3 respectively. The two CipherSchemes require different key material. The Key Derivation Function (KDF) is described in section 3.2.1.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS32-0045
• Source document: source document page 10
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-236

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

CQ-BOUNDARY-237

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

CQ-BOUNDARY-238

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

CQ-BOUNDARY-239

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

CQ-BOUNDARY-24

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

CQ-BOUNDARY-240

• Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: 0x84 0x02 xx x X+1 SDT APAR 0x84 0x02 xx x X+1 0xC4 0x02 xxxxxxxxxx x Y+1 0xC4 0x02 xxxxxxxxxx x Y+1 SDTPR APAR RDBI SNOETDID 0 633132 KeyrequestHKDF(ikm, salt, info, 64) -> C TAG || CHACHA20-POLY1305enrypt(Keyrequest, N, A, P)-> CHACHA20-POLY1305decrypt(Keyrequest, N, A, C, TAG)-> S Keyresponse SecuredDataTransmissionKey (ikm) from 0x29 service Client s state variables PREQTAG=TAG_X Server s state variables C 0x22 || Application layer P A || || RDBI0x22 Application layer SNOETDID S C TAG P A CHACHA20-POLY1305enrypt(Keyresponse, N, A, P)-> RDBIPR0x62 0xF19743564320435 64331 SNOETDID Application layer || C TAG S C 6 A || CHACHA20-POLY1305decrypt(Keyresponse, N, A, C, TAG)-> || || RDBIPR SNOETDID 0x62 0xF19743564320435 64331 Application layer S P P ||X+1 N ||X+1 N Y+1 || N ||Y+1 Figure 6 – Example of client and server's behavior using SDT_AEAD_CHACHA20_POLY1305 The example in Figure 6 shows an AEAD_CHACHA20_POLY1305 authenticated and encrypted SDT transaction.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS32-0086
• Source document: source document page 14
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-241

• Question: Confirm the required ECU-side key/certificate behavior and the customer-owned PKI responsibilities for this item: 0x84 0x03 0x22 X+1 SDT APAR 0x84 0x03 0x22 X+1 0xC4 0x03 0xF1974356432043564331 0x62 Y+1 0xC4 0x03 0xF1974356432043564331 0x62 Y+1 SDTPR APAR 0 633132 KeyrequestHKDF(ikm, salt, info, 64) -> null TAG || CHACHA20-POLY1305authenticate(Keyrequest, N, A, null)-> CHACHA20-POLY1305verify(Keyrequest, N, A, null, TAG)-> ok Keyresponse SecuredDataTransmissionKey (ikm) from 0x29 service Client s state variables PREQTAG=TAG_X Server s state variables A || TAG A CHACHA20-POLY1305authenticate(Keyresponse, N, A, null)-> || null TAG 8 A CHACHA20-POLY1305verify(Keyrequest, N, A, null, TAG)-> ok || TAG A 8 ||X+1 N ||X+1 N ||Y+1 N ||Y+1 N Figure 8 – Example of client and server's behavior using SDT_POLY1305 The example in Figure 8 shows an AEAD_CHACHA20_POLY1305 authenticated SDT transaction.. This affects secure storage, provisioning, renewal/revocation, and CIA/RASIC ownership.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS32-0112
• Source document: source document page 17
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-242

• Question: Confirm the binding diagnostic behavior and service authorization expected for this item: This specification is mainly concerned with errors generated or detected by the client and server’s security sub-layer [1]. General UDS error handling is out of scope of this document. Figure 9 shows how the different “layers”1 interact conceptually.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS32-0114
• Source document: source document page 18
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-243

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

CQ-BOUNDARY-244

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

CQ-BOUNDARY-25

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

CQ-BOUNDARY-26

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

CQ-BOUNDARY-27

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

CQ-BOUNDARY-28

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

CQ-BOUNDARY-29

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

CQ-BOUNDARY-30

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

CQ-BOUNDARY-31

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

CQ-BOUNDARY-32

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

CQ-BOUNDARY-33

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

CQ-BOUNDARY-34

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

CQ-BOUNDARY-35

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

CQ-BOUNDARY-36

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

CQ-BOUNDARY-37

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

CQ-BOUNDARY-38

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

CQ-BOUNDARY-39

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

CQ-BOUNDARY-40

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

CQ-BOUNDARY-41

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

CQ-BOUNDARY-42

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

CQ-BOUNDARY-43

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

CQ-BOUNDARY-44

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

CQ-BOUNDARY-45

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

CQ-BOUNDARY-46

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

CQ-BOUNDARY-47

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

CQ-BOUNDARY-48

• Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: TRATON Software Update Variant 2 (SUV2) sequence Foreword This Commercial Vehicle Standard (“CVS123-2”) contains requirement specifications for TRATON Group and may be referred to by any of its commercial vehicle Affiliates.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS123-2-0001
• Source document: source document page 1
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Assumption
• Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-49

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

CQ-BOUNDARY-50

• Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: While the requirements are applicable for programmable servers, some of the programming steps outlined in this specification (CommunicationControl and ControlDTCSetting) do not primarily target the programmable ECU, but the other ECUs on the same network which need to support the programming of the targeted ECU.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS123-2-0006
• Source document: source document page 4
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-51

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

CQ-BOUNDARY-52

• Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: With a single server objective, an ECU will appear to be programmable through communication with a single diagnostic server even if the ECU in fact implements two or more diagnostic servers – one in the boot loader and one in each application – and in reality will be programmed through communication with either one of them or both.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS123-2-0009
• Source document: source document page 4
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-53

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

CQ-BOUNDARY-54

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

CQ-BOUNDARY-55

• Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: In both cases, whenever the term “ECU supplier” or just “supplier” is used in this specification it refers to the company and organization which is responsible for the implementation and delivery of the ECU according to the requirements in this specification.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS123-2-0016
• Source document: source document page 5
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-56

• Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The following documents are normative and indispensable for the application of this document: • ISO14229-1:2020, Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements • CVS124, Traton Specification on Unified diagnostic services (UDS) requirements • CVS154, DSC Specification • CVS31, Authenticate 0x29 • CVS36, Secure ECU Parametrization • CVS32, SecuredDataTranmission 0x84 • CVS33, Entity Management Protocol (EMP) • CVS34, Entity Management Protocol (EMP) Basic Entity Definition. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS123-2-0017
• Source document: source document page 5
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-57

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

CQ-BOUNDARY-58

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

CQ-BOUNDARY-59

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

CQ-BOUNDARY-60

• Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: Boot loaders need to be updated by the vehicle manufacturer on aftermarket workshop scenarios or at a test bench during component testing, when the ECU is mounted in a vehicle during system testing or in production to fix bugs.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS123-2-0045
• Source document: source document page 9
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-61

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

CQ-BOUNDARY-62

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

CQ-BOUNDARY-63

• Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: It is within the scope of this specification that flash files delivered from the supplier can be encrypted by the vehicle manufacturer before storing in the vehicle manufacturer offboard database, but the server decryption of the received data will always restore it to servers memory into original data delivered by the supplier.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS123-2-0063
• Source document: source document page 11
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-64

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

CQ-BOUNDARY-65

• Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: Each programming step will specify an addressing method (physical or functional), an SPRMIB (suppressPosRspMsgIndicationBit) bit value and other parameter values for the service(s) posted by the client.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS123-2-0074
• Source document: source document page 12
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-66

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

CQ-BOUNDARY-67

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

CQ-BOUNDARY-68

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

CQ-BOUNDARY-69

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

CQ-BOUNDARY-70

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

CQ-BOUNDARY-71

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

CQ-BOUNDARY-72

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

CQ-BOUNDARY-73

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

CQ-BOUNDARY-74

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

CQ-BOUNDARY-75

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

CQ-BOUNDARY-76

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

CQ-BOUNDARY-77

• Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: From this point, onwards (throughout the entire programming sequence) the client posts functionally addressed TesterPresent (0x3E) service requests at regular intervals, with the SPRMIB set, with the purpose to make the server(s) stay in the currently active non-default session and maintain its authenticated state.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS123-2-0099
• Source document: source document page 15
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-78

• Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The client disables the setting of DTCs in each server by posting a functionally addressed ControlDTCSetting (0x85) service request with the sub-function parameter DTCSettingType set to off and the SPRMIB set.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS123-2-0100
• Source document: source document page 15
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-79

• Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: If the server is executing in the boot loader it will accept the request without performing any action, as DTCs are already disabled (DTC setting not supported by boot loader).. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
• Priority: P3
• Decision Type: Product Boundary
• Workshop Block: Block 1: Product and Boundary
• Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
• Impact if unresolved: Can remain as tracked assumption
• Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
• Related Related requirements: RFQX-CVS123-2-0101
• Source document: source document page 15
• Related architecture/security element: System boundary / item definition
• Recommended owner: Joint
• Current RFQX status: Reclassified as Informational
• Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
• Classification: Needs Customer Clarification

CQ-BOUNDARY-80

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

CQ-BOUNDARY-81

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