Diagram Image Extraction Audit

Per-diagram image availability and extraction strategy audit.

Last updated: 2026-06-29 11:49
RTRFQX Review TeamWorkspace

Diagram Image Extraction Audit

Per-diagram image availability and extraction strategy audit.

Per-diagram image availability and extraction strategy audit.

Generated reportUpdated 2026-06-29 11:47

Diagram Image Extraction Audit

PDF image extraction is performed only during PDF-to-Markdown conversion. Downstream artifact linking uses Markdown and converted/assets/image_manifest.json only.

  • Current converter/library: conversion-stage image extractor plus configured text converter
  • Converter currently exports embedded images: yes
  • Converter currently exports page screenshots/regions: yes, for figure/diagram candidate pages
  • Images extracted: 121
  • Images ignored as decorative/small: 167
  • Diagram artifacts currently lacking image assets: 0
Source PDFPageSectionDiagram artifact IDCaption / nearby textCurrent image assetExpected image assetExtraction candidateCurrent Markdown image referenceProblemFix strategy
3299216_1.pdfpage 63.4 The PP and AP are moving in one direction parallel to the axis “X”. X=0 where the AP is at itsDIAGRAM-32992161-0001Figure 1 - Position definitionconverted/assets/by_pdf/3299216-1/images/page-006-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-006-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 73.6 In Figure 2 - Position relations, the behavior of PP and AP can be seen throughout a stroke.DIAGRAM-32992161-0002Figure 2 - Position relationsconverted/assets/by_pdf/3299216-1/images/page-007-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-007-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 84.3 The clutch actuator shall be able to reach the extreme positions A and B in with the center ofDIAGRAM-32992161-0003Figure 3 - Pushrod positionsconverted/assets/by_pdf/3299216-1/images/page-008-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-008-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 94.4 ECA shall not interfere with any geometry in the 3D envelope 53612101-1 1_RFQ2030.stpDIAGRAM-32992161-0004Figure 4 – ISO view of 3d envelope. (all parts not shown)converted/assets/by_pdf/3299216-1/images/page-009-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-009-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 104.9 The ECA shall be adapted for 2 pcs 10 mm guide pins.DIAGRAM-32992161-0005Figure 5 - Gearbox flangeconverted/assets/by_pdf/3299216-1/images/page-010-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-010-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 114.18 When the cover is assembled it shall not be possible to insert an object larger than Ø0,2 mmDIAGRAM-32992161-0006Figure 6 - Snap in tool spaceconverted/assets/by_pdf/3299216-1/images/page-011-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-011-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 135.1 It shall be possible to disengage the clutch in 180ms (= Ts) with accuracy according to reqDIAGRAM-32992161-0007Figure 7 – Maximum disengage timeconverted/assets/by_pdf/3299216-1/images/page-013-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-013-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 145.2 It shall be possible to engage the clutch in 180ms (=Ts) with accuracy according to re q.5.10,DIAGRAM-32992161-0008Figure 8 - Maximum engage timeconverted/assets/by_pdf/3299216-1/images/page-014-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-014-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 165.10 The actuator shall move the pushrod according to the following points:DIAGRAM-32992161-0009Figure 9 - Step response.converted/assets/by_pdf/3299216-1/images/page-016-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-016-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 165.2 and this section.DIAGRAM-32992161-0010Figure 9 - Step responseconverted/assets/by_pdf/3299216-1/images/page-016-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-016-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 175.11 Req. 5.10 shall be tested with a step response test cycle, according to description and FigureDIAGRAM-32992161-0011Figure 10 - Step response test cycleconverted/assets/by_pdf/3299216-1/images/page-017-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-017-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 185.12 The ECA shall be able to run the 4 second test cycle in Figure 11 - Release frequency testDIAGRAM-32992161-0012Figure 11 - Release frequency testconverted/assets/by_pdf/3299216-1/images/page-018-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-018-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 195.13 Under some conditions the requirements for disengage and engage strokes (See req. 5.1, req.DIAGRAM-32992161-0013Figure 12 - Class B exceptionsconverted/assets/by_pdf/3299216-1/images/page-019-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-019-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 297.20 Peak current (Ipeak): - - SeeDIAGRAM-32992161-0014Figure 133 A 3. Up to 100 kHzconverted/assets/by_pdf/3299216-1/images/page-029-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-029-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 307.21 Inrush currentDIAGRAM-32992161-0015Figure 13 - Max currentconverted/assets/by_pdf/3299216-1/images/page-030-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-030-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 327.31 Hysteresis: 1 - - VDIAGRAM-32992161-0016Figure 13 - Wake up signal hysteresisconverted/assets/by_pdf/3299216-1/images/page-032-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-032-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 337.33 Dual function block diagram as per Figure 14.DIAGRAM-32992161-0017Figure 14 – Dual function block diagramconverted/assets/by_pdf/3299216-1/images/page-033-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-033-img-001.png; converted/assets/by_pdf/3299216-1/images/page-033-img-002.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 347.38 Baud rate forDIAGRAM-32992161-0018Figure 15 - Reference circuitconverted/assets/by_pdf/3299216-1/images/page-034-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-034-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 378.1 In Figure 16, the average temperature profile for all trucks is shown. Specific vehicles can runDIAGRAM-32992161-0019Figure 16 - Temperature histogramconverted/assets/by_pdf/3299216-1/images/page-037-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-037-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 4110.4 For this unit, the following definitions of test procedure I and test procedure II shall be used:DIAGRAM-32992161-0020Figure 17 - Test procedure Iconverted/assets/by_pdf/3299216-1/images/page-041-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-041-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 5514.33 CVS10 Traton customer requirementsDIAGRAM-32992161-0021Figure 18 - Disengage forceconverted/assets/by_pdf/3299216-1/images/page-055-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-055-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 5614.33 CVS10 Traton customer requirementsDIAGRAM-32992161-0022Figure 19 - Engage forceconverted/assets/by_pdf/3299216-1/images/page-056-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-056-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 5814.33 CVS10 Traton customer requirementsDIAGRAM-32992161-0023Figure 20 - Test cycleconverted/assets/by_pdf/3299216-1/images/page-058-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-058-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 6014.33 CVS10 Traton customer requirementsDIAGRAM-32992161-0024Figure 21 – Release Load vs Strokesconverted/assets/by_pdf/3299216-1/images/page-060-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-060-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
3299216_1.pdfpage 6114.33 CVS10 Traton customer requirementsDIAGRAM-32992161-0025Figure 22 – Release Load vs Strokesconverted/assets/by_pdf/3299216-1/images/page-061-img-001.pngconverted/assets/by_pdf/3299216-1/images/page-061-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS123-2.pdfpage 52.3 Relation to other specificationsDIAGRAM-CVS1232-0001Figure 1: Overview of relation between specificationsconverted/assets/by_pdf/cvs123-2/images/page-005-img-001.pngconverted/assets/by_pdf/cvs123-2/images/page-005-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS123-2.pdfpage 135.1.1 Pre-programming step of phase #1 – Setup vehicle network for programmingDIAGRAM-CVS1232-0002Figure 2: Programming Phase #1 - Pre-Programming Stepconverted/assets/by_pdf/cvs123-2/images/page-013-img-001.pngconverted/assets/by_pdf/cvs123-2/images/page-013-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS123-2.pdfpage 165.1.2 Programming step of phase #1 – Download of application software and dataDIAGRAM-CVS1232-0003Figure 3: Programming phase #1 – Programming stepconverted/assets/by_pdf/cvs123-2/images/page-016-img-001.pngconverted/assets/by_pdf/cvs123-2/images/page-016-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS123-2.pdfpage 195.1.3 Post-Programming step of phase #1 — Re-synchronization of vehicle networkDIAGRAM-CVS1232-0004Figure 4: Programming phase #1 – Post-Programming stepconverted/assets/by_pdf/cvs123-2/images/page-019-img-001.pngconverted/assets/by_pdf/cvs123-2/images/page-019-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS123-2.pdfpage 388.4.4.3 Parameter routineResultProofDIAGRAM-CVS1232-0005Figure 5: diagram for signing of software update resultsconverted/assets/by_pdf/cvs123-2/images/page-038-img-001.pngconverted/assets/by_pdf/cvs123-2/images/page-038-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS123-2.pdfpage 419.2 Software VerificationDIAGRAM-CVS1232-0006Figure 6: Erased-only bytes of a memory moduleconverted/assets/by_pdf/cvs123-2/images/page-041-img-001.pngconverted/assets/by_pdf/cvs123-2/images/page-041-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS123-2.pdfpage 479.3 Software decryptionDIAGRAM-CVS1232-0007Figure 7 – Received ECU Memory Layoutconverted/assets/by_pdf/cvs123-2/images/page-047-img-001.pngconverted/assets/by_pdf/cvs123-2/images/page-047-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS123-2.pdfpage 4700AFAAABDIAGRAM-CVS1232-0008Figure 8 – Memory layoutconverted/assets/by_pdf/cvs123-2/images/page-047-img-001.pngconverted/assets/by_pdf/cvs123-2/images/page-047-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS123-2.pdfpage 4800AFAAABDIAGRAM-CVS1232-0009Figure 9 – Resulting SDSC content transmitted using EMPconverted/assets/by_pdf/cvs123-2/images/page-048-img-001.pngconverted/assets/by_pdf/cvs123-2/images/page-048-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS123-2.pdfpage 4900AFAAABDIAGRAM-CVS1232-0010Figure 10 - Verification Entry for Module Cconverted/assets/by_pdf/cvs123-2/images/page-049-img-001.pngconverted/assets/by_pdf/cvs123-2/images/page-049-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS123-2.pdfpage 5000AFAAABDIAGRAM-CVS1232-0011Figure 11 – Memory layoutconverted/assets/by_pdf/cvs123-2/images/page-050-img-001.pngconverted/assets/by_pdf/cvs123-2/images/page-050-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS123-2.pdfpage 5100AFAAABDIAGRAM-CVS1232-0012Figure 12 – Resulting SDSC contentconverted/assets/by_pdf/cvs123-2/images/page-051-img-001.pngconverted/assets/by_pdf/cvs123-2/images/page-051-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS123-2.pdfpage 5200AFAAABDIAGRAM-CVS1232-0013Figure 13 – Memory layoutconverted/assets/by_pdf/cvs123-2/images/page-052-img-001.pngconverted/assets/by_pdf/cvs123-2/images/page-052-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS124.pdfpage 55.10 Session layer performance requirements 83DIAGRAM-CVS124-0001Figure 1 - Overview of relation between specificationsconverted/assets/by_pdf/cvs124/images/page-005-img-001.pngconverted/assets/by_pdf/cvs124/images/page-005-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS124.pdfpage 275.3 Diagnostic sessions requirementsDIAGRAM-CVS124-0002Figure 2 -State Diagramconverted/assets/by_pdf/cvs124/images/page-027-img-001.pngconverted/assets/by_pdf/cvs124/images/page-027-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS151.pdfpage 43.1 OverviewDIAGRAM-CVS151-0001Figure 1 – Overviewconverted/assets/by_pdf/cvs151/images/page-004-img-001.pngconverted/assets/by_pdf/cvs151/images/page-004-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS151.pdfpage 43.1 OverviewDIAGRAM-CVS151-0002Figure 1 shows a highlevel view of the RBAC concept.converted/assets/by_pdf/cvs151/images/page-004-img-001.pngconverted/assets/by_pdf/cvs151/images/page-004-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS151.pdfpage 73.2 Role Based Access Control ConfigurationDIAGRAM-CVS151-0003Figure 2 – Visual representation of the RBACCconverted/assets/by_pdf/cvs151/images/page-007-img-001.pngconverted/assets/by_pdf/cvs151/images/page-007-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS151.pdfpage 123.12 LogicDIAGRAM-CVS151-0004Figure 3 shows the interaction between the diagnostics server and the RBAC enforcer logic.converted/assets/by_pdf/cvs151/images/page-012-img-001.pngconverted/assets/by_pdf/cvs151/images/page-012-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS151.pdfpage 133.12 LogicDIAGRAM-CVS151-0005Figure 3 – Logic Overviewconverted/assets/by_pdf/cvs151/images/page-013-img-001.pngconverted/assets/by_pdf/cvs151/images/page-013-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS151.pdfpage 143.12 LogicDIAGRAM-CVS151-0006Figure 4 – RBAC internal logicconverted/assets/by_pdf/cvs151/images/page-014-img-001.pngconverted/assets/by_pdf/cvs151/images/page-014-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS151.pdfpage 153.12 LogicDIAGRAM-CVS151-0007Figure 5 – Pattern-rules evaluationconverted/assets/by_pdf/cvs151/images/page-015-img-001.pngconverted/assets/by_pdf/cvs151/images/page-015-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS151.pdfpage 163.12 LogicDIAGRAM-CVS151-0008Figure 6 – DID-rules evaluationconverted/assets/by_pdf/cvs151/images/page-016-img-001.pngconverted/assets/by_pdf/cvs151/images/page-016-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS151.pdfpage 173.12 LogicDIAGRAM-CVS151-0009Figure 7 – RID-rules evaluationconverted/assets/by_pdf/cvs151/images/page-017-img-001.pngconverted/assets/by_pdf/cvs151/images/page-017-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS151.pdfpage 183.12 LogicDIAGRAM-CVS151-0010Figure 8 – The full rule evaluation scheme (Figure 5 Figure 6, Figure 7 tied together)converted/assets/by_pdf/cvs151/images/page-018-img-001.pngconverted/assets/by_pdf/cvs151/images/page-018-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS151.pdfpage 224.1 Normative referencesDIAGRAM-CVS151-0011Figure 9 – Updating the RBACC using EMPconverted/assets/by_pdf/cvs151/images/page-022-img-001.pngconverted/assets/by_pdf/cvs151/images/page-022-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS151.pdfpage 264.1 Normative referencesDIAGRAM-CVS151-0012Figure 10 – Exampleconverted/assets/by_pdf/cvs151/images/page-026-img-001.pngconverted/assets/by_pdf/cvs151/images/page-026-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS154.pdfpage 34.2 Informative references . 12DIAGRAM-CVS154-0001Figure 1 – Specification relationshipconverted/assets/by_pdf/cvs154/images/page-003-img-001.pngconverted/assets/by_pdf/cvs154/images/page-003-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS154.pdfpage 43.1 DSC structureDIAGRAM-CVS154-0002Figure 2converted/assets/by_pdf/cvs154/images/page-004-img-001.pngconverted/assets/by_pdf/cvs154/images/page-004-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS154.pdfpage 43.1 DSC structureDIAGRAM-CVS154-0003Figure 2 – DSC structureconverted/assets/by_pdf/cvs154/images/page-004-img-001.pngconverted/assets/by_pdf/cvs154/images/page-004-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS154.pdfpage 63.1.1.1 HashCmpDIAGRAM-CVS154-0004Figure 3 – HashCmpconverted/assets/by_pdf/cvs154/images/page-006-img-001.pngconverted/assets/by_pdf/cvs154/images/page-006-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS154.pdfpage 73.1.2.1 AESCTR128DIAGRAM-CVS154-0005Figure 4 – AESCTR128converted/assets/by_pdf/cvs154/images/page-007-img-001.pngconverted/assets/by_pdf/cvs154/images/page-007-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS154.pdfpage 83.1.2.2 CHACHA20DIAGRAM-CVS154-0006Figure 4 – ChaCha20converted/assets/by_pdf/cvs154/images/page-008-img-001.pngconverted/assets/by_pdf/cvs154/images/page-008-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS154.pdfpage 93.1.3 ItemEntryDIAGRAM-CVS154-0007Figure 5 – Item listconverted/assets/by_pdf/cvs154/images/page-009-img-001.pngconverted/assets/by_pdf/cvs154/images/page-009-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS154.pdfpage 134.2 Informative referencesDIAGRAM-CVS154-0008Figure 6 – DSC sanity check and verificationconverted/assets/by_pdf/cvs154/images/page-013-img-001.pngconverted/assets/by_pdf/cvs154/images/page-013-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS31.pdfpage 41.1 SummaryDIAGRAM-CVS31-0001Figure 1 – Overview of relation between specificationsconverted/assets/by_pdf/cvs31/images/page-004-img-001.pngconverted/assets/by_pdf/cvs31/images/page-004-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS31.pdfpage 51.1 SummaryDIAGRAM-CVS31-0002Figure 2 – Security concepts (ISO 14229-1:2020)converted/assets/by_pdf/cvs31/images/page-005-img-001.pngconverted/assets/by_pdf/cvs31/images/page-005-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS31.pdfpage 174.1 CertificateDIAGRAM-CVS31-0003Figure 3 – Client certificate validation logicconverted/assets/by_pdf/cvs31/images/page-017-img-001.pngconverted/assets/by_pdf/cvs31/images/page-017-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS31.pdfpage 224.3 SessionKeyDIAGRAM-CVS31-0004Figure 4 – Overview Ephemeral Diffie-Hellman key-exchangeconverted/assets/by_pdf/cvs31/images/page-022-img-001.pngconverted/assets/by_pdf/cvs31/images/page-022-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS31.pdfpage 254.9 Authentication completion timerDIAGRAM-CVS31-0005Figure 5 – Overviewconverted/assets/by_pdf/cvs31/images/page-025-img-001.pngconverted/assets/by_pdf/cvs31/images/page-025-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS31.pdfpage 264.9 Authentication completion timerDIAGRAM-CVS31-0006Figure 6 – Server Handling of Signatureconverted/assets/by_pdf/cvs31/images/page-026-img-001.pngconverted/assets/by_pdf/cvs31/images/page-026-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS31.pdfpage 284.9 Authentication completion timerDIAGRAM-CVS31-0007Figure 7 – Authentication State Transitionconverted/assets/by_pdf/cvs31/images/page-028-img-001.pngconverted/assets/by_pdf/cvs31/images/page-028-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 61.5 TerminologyDIAGRAM-CVS32-0001Figure 1 – SDT Overviewconverted/assets/by_pdf/cvs32/images/page-006-img-001.pngconverted/assets/by_pdf/cvs32/images/page-006-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 61.5 TerminologyDIAGRAM-CVS32-0002Figure 1 shows the layout of an SDT message with its protocol elements (for details refer toconverted/assets/by_pdf/cvs32/images/page-006-img-001.pngconverted/assets/by_pdf/cvs32/images/page-006-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 83.1 Anti-replay Protection and Transaction CoherencyDIAGRAM-CVS32-0003Figure 2 – Anti-replay protectionconverted/assets/by_pdf/cvs32/images/page-008-img-001.pngconverted/assets/by_pdf/cvs32/images/page-008-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 93.1 Anti-replay Protection and Transaction CoherencyDIAGRAM-CVS32-0004Figure 3 – Anti-replay protection and transaction coherencyconverted/assets/by_pdf/cvs32/images/page-009-img-001.pngconverted/assets/by_pdf/cvs32/images/page-009-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 93.1 Anti-replay Protection and Transaction CoherencyDIAGRAM-CVS32-0005Figure 3 illustrates transaction coherency and the use of PREQTAG. To avoid mix-up, theconverted/assets/by_pdf/cvs32/images/page-009-img-001.pngconverted/assets/by_pdf/cvs32/images/page-009-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 113.2 Authenticity and ConfidentialityDIAGRAM-CVS32-0006Figure 4 illustrates the switching of CipherSchemes within an SDT sequence. The client hasconverted/assets/by_pdf/cvs32/images/page-011-img-001.pngconverted/assets/by_pdf/cvs32/images/page-011-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 113.2 Authenticity and ConfidentialityDIAGRAM-CVS32-0007Figure 4 – Change of CipherScheme mid sequenceconverted/assets/by_pdf/cvs32/images/page-011-img-001.pngconverted/assets/by_pdf/cvs32/images/page-011-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 123.2.2 SDT_AEAD_CHACHA20_POLY1305DIAGRAM-CVS32-0008Figure 5 – Use of HKDF output key material (okm) with SDT_CHACHA20_POLY1305converted/assets/by_pdf/cvs32/images/page-012-img-001.pngconverted/assets/by_pdf/cvs32/images/page-012-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 143.2.2.2 Server Decryption/EncryptionDIAGRAM-CVS32-0009Figure 6 – Example of client and server's behavior using SDT_AEAD_CHACHA20_POLY1305converted/assets/by_pdf/cvs32/images/page-014-img-001.pngconverted/assets/by_pdf/cvs32/images/page-014-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 153.2.3 SDT_POLY1305DIAGRAM-CVS32-0010Figure 7 – Use of HKDF output key material (okm) with SDT_POLY1305converted/assets/by_pdf/cvs32/images/page-015-img-001.pngconverted/assets/by_pdf/cvs32/images/page-015-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 173.2.3.2 Server Verification/AuthenticationDIAGRAM-CVS32-0011Figure 8 – Example of client and server's behavior using SDT_POLY1305converted/assets/by_pdf/cvs32/images/page-017-img-001.pngconverted/assets/by_pdf/cvs32/images/page-017-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 183.3 Error- and state-handlingDIAGRAM-CVS32-0012Figure 9 shows how the different “layers”1 interact conceptually.converted/assets/by_pdf/cvs32/images/page-018-img-001.pngconverted/assets/by_pdf/cvs32/images/page-018-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 183.3 Error- and state-handlingDIAGRAM-CVS32-0013Figure 9 – Conceptual overview of SDT error handlingconverted/assets/by_pdf/cvs32/images/page-018-img-001.pngconverted/assets/by_pdf/cvs32/images/page-018-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 183.3.1 Server’s BehaviourDIAGRAM-CVS32-0014Figure 10Figure 10 illustrates error- and state handling in the server’s security sub-layer. Theconverted/assets/by_pdf/cvs32/images/page-018-img-001.pngconverted/assets/by_pdf/cvs32/images/page-018-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 193.3.1 Server’s BehaviourDIAGRAM-CVS32-0015Figure 10 – Server's error and state handlingconverted/assets/by_pdf/cvs32/images/page-019-img-001.pngconverted/assets/by_pdf/cvs32/images/page-019-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 213.3.1.1 SDT transactions with multiple responsesDIAGRAM-CVS32-0016Figure 11 shows an example where the client sends a RDBI and the server responds with twoconverted/assets/by_pdf/cvs32/images/page-021-img-001.pngconverted/assets/by_pdf/cvs32/images/page-021-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 213.3.1.1 SDT transactions with multiple responsesDIAGRAM-CVS32-0017Figure 11 – Example of a multi-response transactionconverted/assets/by_pdf/cvs32/images/page-021-img-001.pngconverted/assets/by_pdf/cvs32/images/page-021-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 213.3.2 Client’s BehaviourDIAGRAM-CVS32-0018Figure 12Figure 12 illustrates error- and state handling in the client’s security sub-layer. Theconverted/assets/by_pdf/cvs32/images/page-021-img-001.pngconverted/assets/by_pdf/cvs32/images/page-021-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 223.3.2 Client’s BehaviourDIAGRAM-CVS32-0019Figure 12 – The client's error and state handlingconverted/assets/by_pdf/cvs32/images/page-022-img-001.pngconverted/assets/by_pdf/cvs32/images/page-022-img-001.pngembedded imageUse conversion-stage image_manifest.json and same page/caption matching
CVS32.pdfpage 293.3.2.1 Lost and Repeated SDT MessagesDIAGRAM-CVS32-0020Figure 9.)converted/assets/by_pdf/cvs32/images/page-029-img-001.pngconverted/assets/by_pdf/cvs32/images/page-029-img-001.pngpage-regionUse conversion-stage image_manifest.json and same page/caption matching