All relays

Paramount stitcher

Paramount

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

QUIC WT drafts 14–20 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-20, h3, 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 20 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
20 QUIC err ok err
19 QUIC err err ok err
18 QUIC err err ok err
17 QUIC 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."

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 20 · QUIC

  • 0x07 moqt_implementation = moq-lite-rs
  • 0x40b55 not defined by this draft = 0xfe19c9a833523881
  • 0x40b5a not defined by this draft = 1

draft 19 · QUIC

  • 0x07 moqt_implementation = moq-lite-rs
  • 0x40b55 not defined by this draft = 0xfe19c9a833523881
  • 0x40b5a not defined by this draft = 1

draft 18 · QUIC

  • 0x07 moqt_implementation = moq-lite-rs
  • 0x40b55 not defined by this draft = 0xfe19c9a833523881
  • 0x40b5a not defined by this draft = 1

draft 17 · QUIC

  • 0x07 moqt_implementation = moq-lite-rs
  • 0x40b55 not defined by this draft = 0xfe19c9a833523881
  • 0x40b5a 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

draft 15 · QUIC

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

draft 14 · QUIC

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

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.