libquicr (quicr.org)
Ciscous-west-2.relay.quicr.org:33437/relay
A deployment of libquicr, operated by Cisco. 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
- us-west-2.relay.public — under 0xf1, which draft 16 does not define
- Protocols accepted
- moqt-16, h3
- Media delivery
- not attempted
- Violations recorded
- 1
Certificate
- Subject
- CN=us-west-2.relay.quicr.org
- Issuer
- C=US, O=Let's Encrypt, CN=E8
- Valid until
- 2026-07-29 expired 47 days ago
- Trust
- expired
- 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 |
|---|---|---|---|---|---|
| 16 QUIC | – | – | – | – | – |
| 15 WT | – | – | – | – | – |
Specification violations
codec error: track property type 2 carries value 0, which is outside the range it allows
What the specification requires
Section 11.1 of the Track Property namespace. DELIVERY_TIMEOUT (0x02): "if present, MUST contain a value greater than 0. If an endpoint receives a DELIVERY_TIMEOUT equal to 0 it MUST close the session with PROTOCOL_VIOLATION." DEFAULT_PUBLISHER_GROUP_ORDER (0x22) and DYNAMIC_GROUPS (0x30) each name their allowed values and the same consequence.
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 16 · QUIC
- 0xf1 not defined by this draft = us-west-2.relay.public
draft 15 · WT
- 0xf1 not defined by this draft = us-west-2.relay.public
Notes
- — QUIC completes only with certificate verification disabled
- — the peer is up but 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.