SkyV2X · Open Testbed Public · Section 4.2 · Conformance Audit 42/47 passing
TLA-VIS-001  v0.2.0  ·  2026-06-21
4.2 Audit

Conformance audit

The ETSI MEC 032-3 Robot Framework suite runs against Talaia and the verdict ships here. 42 of 47 test cases passing.

4.2.1Verdict

Current verdict

Three values from the audit run, taken directly from /vis/v2/conformance.

Passing

42 / 47

clean baseline

Spec under test

MEC 030

V3.2.1 spec-strict

Suite

032-3

Robot Framework

Each cell below represents one test case in the suite. Filled cells passed at the last run; outlined cells are pending.

Passing (42) Pending (5)
4.2.2Method

Method

ETSI GS MEC 032-3 is the conformance specification for the V2X Information Service. It defines test purposes any V2XIS implementation must pass — request shapes, response codes, error formats, subscription lifecycle, broker discovery. The companion Robot Framework artefact at the ETSI Forge packages those purposes as executable tests.

The audit harness runs the suite against Talaia, parses the Robot output, and exposes the verdict at /vis/v2/conformance. The numbers in 4.2.1 come straight from that endpoint.

4.2.3Passing

What passes

  • Resource discovery. The eight V2XIS endpoints respond at the spec-mandated paths with the correct response codes.
  • ProblemDetails. Every 4xx and 5xx carries application/problem+json with the four required fields and an instance pointer.
  • Provisioning queries. Uu unicast, Uu MBMS and PC5 provisioning info return spec-shaped payloads under location_info filtering.
  • Subscription registry. Create, read, update and delete over the subscription resources, with persistent state and the mandated Location headers.
  • Tasks. Message publication, predicted QoS and distribution-server-info return the required shapes and status codes.
4.2.4Pending

What remains

  • Pre-provisioned fixtures. Four cases delete subscriptions the suite assumes already exist; they pass once those fixtures are seeded (46/47).
  • Suite contradiction. One case asks for different status codes on two opaque, indistinguishable error strings — recorded as a documented deviation, not a gap.
4.2.5Rationale

Why publish

Commercial MEC platforms claiming ETSI conformance ask the integrator to trust the claim — there is rarely a third-party audit. Talaia publishes the audit instead: the public ETSI suite, run against the live endpoints, with the verdict on this page.

The run is reproducible and the five remaining failures are documented rather than hidden.

Source documents: ETSI GS MEC 030 V3.2.1 [1], ETSI GS MEC 032-3 [6].