Nokia Research draft-18
Nokiamoqt.nokiaresearch.com:8443/moq
Operated by Nokia. The implementation running here has not been published, so everything below describes this endpoint and nothing else. About this endpoint
At a glance
- Identifies itself as
- StreamForge MOQ v19
- Protocols accepted
- moqt-19, h3, moqt-18
- Media delivery
- delivered, first object 2ms
- Violations recorded
- 3
Certificate
- Subject
- C=FI, L=Espoo, O=Nokia Oyj, CN=*.nokiaresearch.com
- Issuer
- C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
- Valid until
- 2027-03-20 136 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 | SUBSCRIBE | FETCH | TRACK_STATUS | SUBSCRIBE_NAMESPACE | PUBLISH_NAMESPACE | SUBSCRIBE_TRACKS | PUBLISH |
|---|---|---|---|---|---|---|---|
| 23 WT | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| 22 WT | ✓ err | ✗ | ✓ err | ✓ ok | ✓ ok | ✓ ok | – |
| 21 WT | ✓ err | ✗ | ✓ err | ✓ ok | ✓ ok | ✓ ok | – |
| 20 WT | ✓ err | ✗ | ✓ err | ✓ ok | ✓ ok | ✓ ok | – |
| 19 QUIC | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | ✓ ok | ✓ ok |
| 18 QUIC | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | ✓ ok | ✓ ok |
| 17 WT | ✗ | ✓ err | ✓ err | ✗ | ✗ | · | ✓ err |
Media delivery
One publisher and two subscribers, to see whether an object published through this endpoint reaches a client that asked for it.
- Objects delivered
- 7/7
- Groups / subgroups
- 2 / 3
- Subscribe answered
- 6ms
- First object
- 2ms
- Stream framing
- streams kept as sent
- Second subscriber
- Same object delivered to a second subscriber
- Offers a track
- relay offered the track
Two publishers of one track
Two publishers announce the same namespace and publish the same tracks, one with identical payloads and one with payloads that differ by publisher. Partway through, the publisher serving the subscribers disconnects without notice. A fresh subscription, sent afterwards, shows whether the remaining publisher could still be reached.
| Publisher | Role | Announcement | Subscribed to | Ended by the relay |
|---|---|---|---|---|
| first publisher disconnected | serving The relay accepted it and subscribed to it. | accepted, REQUEST_OK in 1 ms | differing payloads, identical payloads | — |
| second publisher | serving The relay accepted it and subscribed to it. | accepted, REQUEST_OK in 2 ms | differing payloads, identical payloads | — |
| Track | Objects | From | When the publisher left | Ended by |
|---|---|---|---|---|
| identical payloads | each object once 43 delivered | — | carried on from the other publisher first object 197 ms after | — |
| differing payloads | each object once 1 delivered | second publisher | ended before the publisher left | PUBLISH_DONE 18 “track or object is malformed: duplicate location with different payload or properties” |
A fresh subscription after the publisher left: delivered, first object in 216 ms.
Specification violations
A message parameter must only appear in the messages its definition names.
Draft 22 over WebTransport, during the control message probe (PUBLISH)
- Specification
- draft-ietf-moq-transport-22, Section 9.20.1
- Required response
- close the session with PROTOCOL_VIOLATION (0x3)
A message parameter must only appear in the messages its definition names.
Draft 21 over WebTransport, during the control message probe (PUBLISH)
- Specification
- draft-ietf-moq-transport-21, Section 9.20.1
- Required response
- close the session with PROTOCOL_VIOLATION (0x3)
A message parameter must only appear in the messages its definition names.
Draft 20 over WebTransport, during the control message probe (PUBLISH)
- Specification
- draft-ietf-moq-transport-20, Section 10.2.1
- Required response
- close the session with PROTOCOL_VIOLATION (0x3)
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 23 · WT
No parameters sent.
draft 22 · WT
- 0x04 max_auth_token_cache_size = 1048576
- 0x06 max_filter_ranges = 64
- 0x07 moqt_implementation = StreamForge MOQ v19
- 0x08 max_request_updates = 8
- 0x09 not defined by this draft = 0x00 (max_control_message_size in 23)
- 0x0a not defined by this draft = 16
draft 21 · WT
- 0x04 max_auth_token_cache_size = 1048576
- 0x06 max_filter_ranges = 64
- 0x07 moqt_implementation = StreamForge MOQ v19
- 0x08 max_request_updates = 8
- 0x09 not defined by this draft = 0x00 (max_control_message_size in 23)
- 0x0a not defined by this draft = 16
draft 20 · WT
- 0x04 max_auth_token_cache_size = 1048576
- 0x06 max_filter_ranges = 64
- 0x07 moqt_implementation = StreamForge MOQ v19
- 0x08 max_request_updates = 8
- 0x09 not defined by this draft = 0x00 (max_control_message_size in 23)
- 0x0a not defined by this draft = 16
draft 19 · QUIC
- 0x04 max_auth_token_cache_size = 1048576
- 0x06 max_filter_ranges = 64
- 0x07 moqt_implementation = StreamForge MOQ v19
- 0x08 max_request_updates = 8
- 0x09 not defined by this draft = 0x00 (max_control_message_size in 23)
- 0x0a not defined by this draft = 16
draft 18 · QUIC
- 0x04 max_auth_token_cache_size = 1048576
- 0x06 not defined by this draft = 64 (max_filter_ranges in 19–23)
- 0x07 moqt_implementation = StreamForge MOQ v19
- 0x08 not defined by this draft = 8 (max_request_updates in 19–23)
- 0x09 not defined by this draft = 0x00 (max_control_message_size in 23)
- 0x0a not defined by this draft = 16
draft 17 · WT
- 0x04 max_auth_token_cache_size = 1048576
- 0x06 not defined by this draft = 64 (max_filter_ranges in 19–23)
- 0x07 moqt_implementation = StreamForge MOQ v19
- 0x08 not defined by this draft = 8 (max_request_updates in 19–23)
- 0x09 not defined by this draft = 0x00 (max_control_message_size in 23)
- 0x0a not defined by this draft = 16
History
9 sweeps, newest first. A step where the probe build or the measuring location changed is marked, and is not read as a change of the relay.
3 Nov 2026 → 4 Nov 2026 · measured differently
- Drafts answered: 17, 18, 19, 20, 21, 22 → 17, 18, 19, 20, 21, 22, 23.
27 Oct 2026 → 29 Oct 2026 · measured differently
- Offering a track: not measured → relay offered the track.
| Sweep | Reachable | Drafts | Delivery | Offers a track | Violations | Two publishers |
|---|---|---|---|---|---|---|
| 5 Nov 2026 | yes | 17, 18, 19, 20, 21, 22, 23 | Object delivered end to end | relay offered the track | 1 | no defects |
| 4 Nov 2026 | yes | 17, 18, 19, 20, 21, 22, 23 | Object delivered end to end | relay offered the track | 1 | no defects |
| 3 Nov 2026 | yes | 17, 18, 19, 20, 21, 22 | Object delivered end to end | relay offered the track | 1 | no defects |
| 2 Nov 2026 | yes | 17, 18, 19, 20, 21, 22 | Object delivered end to end | relay offered the track | 1 | no defects |
| 1 Nov 2026 | yes | 17, 18, 19, 20, 21, 22 | Object delivered end to end | relay offered the track | 1 | no defects |
| 31 Oct 2026 | yes | 17, 18, 19, 20, 21, 22 | Object delivered end to end | relay offered the track | 1 | no defects |
| 30 Oct 2026 | yes | 17, 18, 19, 20, 21, 22 | Object delivered end to end | relay offered the track | 1 | no defects |
| 29 Oct 2026 | yes | 17, 18, 19, 20, 21, 22 | Object delivered end to end | relay offered the track | 1 | no defects |
| 27 Oct 2026 | yes | 17, 18, 19, 20, 21, 22 | Object delivered end to end | — | 1 | — |
Notes
- — The endpoint is up and refused the offered protocols on at least one transport.
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.