All relays

Paramount stitcher

Paramount

34-72-6-160.sslip.io:443

QUIC WT drafts 14–22 IPv4

A deployment of moq.dev, operated by Paramount. Everything below was measured on this deployment, at whatever version and configuration it was running — it is not a measurement of that codebase. About this endpoint

At a glance

Identifies itself as
moq-lite-rs
Protocols accepted
moqt-22, h3, moqt-21, moqt-20, moqt-19, moqt-18, moqt-17, moqt-16, moqt-15, moq-00
Media delivery
not attempted
Violations recorded
1

Certificate

Subject
CN=34-72-6-160.sslip.io
Issuer
C=AT, O=ZeroSSL GmbH, CN=ZeroSSL ECC DV SSL CA 2
Valid until
2026-10-04 2 days left
Trust
publicly-trusted
Verification
Completed with the certificate verified

Control messages

Which control messages this endpoint answered, per draft. An error reply is still an answer — ok and err are both support; what is recorded as missing is a message that got no answer at all. A dash is neither: it means the exchange ended on our side, so nothing about this endpoint was measured there.

Draft SUBSCRIBEFETCHTRACK_STATUSSUBSCRIBE_NAMESPACEPUBLISH_NAMESPACE
22 QUIC ✓ err ✗ ✓ err ✓ ok ✓ err
21 QUIC ✓ err ✗ ✓ err ✓ ok ✓ err
20 QUIC ✓ err ✗ ✓ err ✓ ok ✓ err
19 QUIC ✓ err ✓ err ✓ err ✓ ok ✓ err
18 QUIC ✓ err ✓ err ✓ err ✓ ok ✓ err
17 QUIC ✓ err ✓ err ✓ err ✓ ok ✓ err
16 QUIC – – – ✓ ok –
15 QUIC – – – – –
14 QUIC – – – – –

Specification violations

request-id-ceiling draft 14 over QUIC, during messages/subscribe

endpoint error: request ID error: request ID 1 exceeds max 0

What the specification requires

draft-14 Section 9.5: "If a Request ID equal to or larger than this is received by the endpoint that sent the MAX_REQUEST_ID in any request message (PUBLISH_NAMESPACE, FETCH, SUBSCRIBE, SUBSCRIBE_NAMESPACE, SUBSCRIBE_UDPATE or TRACK_STATUS), the endpoint MUST close the session with an error of TOO_MANY_REQUESTS." What this endpoint did, which the draft's sentence does not cover: outside the delivery measurement it sends no MAX_REQUEST_ID of its own, so the Maximum Request ID it grants the relay is 0 — the lowest the parameter has — and the relay's own requests are bounded at 0 from the first message of the session. That is deliberate rather than an oversight: offering nothing is what keeps the parameter probe's offered-nothing baseline a baseline. The delivery sessions grant 100 instead, and this row's own words name whichever number applied. The charge is for exceeding a ceiling this endpoint published, not for publishing a restrictive one. Drafts 15 and 16 are charged nothing at all here: they answer this one event with INVALID_REQUEST_ID in one section and TOO_MANY_REQUESTS in another, and no relay can be on the wrong side of both.

Setup parameters

What this endpoint sent back in its setup response, per draft. A parameter with no name is a code point the negotiated draft does not define.

draft 22 · QUIC

  • 0x07 moqt_implementation = moq-lite-rs
  • 0x40b54 not defined by this draft = 4197405198214099
  • 0x40b5a not defined by this draft = 1
  • 0x40b5c not defined by this draft = 1

draft 21 · QUIC

  • 0x07 moqt_implementation = moq-lite-rs
  • 0x40b54 not defined by this draft = 4197405198214099
  • 0x40b5a not defined by this draft = 1
  • 0x40b5c not defined by this draft = 1

draft 20 · QUIC

  • 0x07 moqt_implementation = moq-lite-rs
  • 0x40b54 not defined by this draft = 4197405198214099
  • 0x40b5a not defined by this draft = 1
  • 0x40b5c not defined by this draft = 1

draft 19 · QUIC

  • 0x07 moqt_implementation = moq-lite-rs
  • 0x40b54 not defined by this draft = 4197405198214099
  • 0x40b5a not defined by this draft = 1
  • 0x40b5c not defined by this draft = 1

draft 18 · QUIC

  • 0x07 moqt_implementation = moq-lite-rs
  • 0x40b54 not defined by this draft = 4197405198214099
  • 0x40b5a not defined by this draft = 1
  • 0x40b5c not defined by this draft = 1

draft 17 · QUIC

  • 0x07 moqt_implementation = moq-lite-rs
  • 0x40b54 not defined by this draft = 4197405198214099
  • 0x40b5a not defined by this draft = 1
  • 0x40b5c not defined by this draft = 1

draft 16 · QUIC

  • 0x02 max_request_id = 4294967295
  • 0x07 moqt_implementation = moq-lite-rs
  • 0x40b5a not defined by this draft = 1
  • 0x40b5c not defined by this draft = 1

draft 15 · QUIC

  • 0x02 max_request_id = 4294967295
  • 0x40b5a not defined by this draft = 1
  • 0x40b5c not defined by this draft = 1
  • 0x07 moqt_implementation = moq-lite-rs

draft 14 · QUIC

  • 0x40b5c not defined by this draft = 1
  • 0x02 max_request_id = 4294967295
  • 0x40b5a not defined by this draft = 1
  • 0x07 not defined by this draft = moq-lite-rs (moqt_implementation in 15–22)

Is this your relay?

If something here is wrong, tell us — we keep what each result rests on, so a disputed one gets re-read rather than re-argued. We can also run this against endpoints that are not public.

Get in touch Debug it yourself