Skip to content

A refused TRACK_STATUS upstream fails a lite TRACK_INFO, so the subscriber never subscribes #7423

Closed as not planned

Description

@michaelstuurman

Behind a moq-transport publisher that refuses TRACK_STATUS on draft 18 (openmoq/moqxr answers it, and FETCH, with NOT_SUPPORTED), a moq-lite-06 subscriber can't start a track through moq-relay on main (e072cf6).

  1. @moq/watch sends TRACK_INFO for catalog before subscribing.
  2. The relay has no copy, so ietf::Subscriber::track_status asks the publisher with TRACK_STATUS.
  3. The publisher refuses with NOT_SUPPORTED, and the query-only request fails ("a refused status fails the query-only or fetch-only request").
  4. The relay logs moq_net::lite::publisher: track info error … track=catalog err=unsupported. The player never sends SUBSCRIBE, so the publisher never sees one.

The same publisher plays through moq-relay 0.17.8, before TRACK_INFO. It also plays through moqx, where the player speaks moq-transport and subscribes without a TRACK_STATUS. Only the moq-lite → moq-transport translation asks for one.

doc/concept/standard.md already says a reader whose publisher refuses TRACK_STATUS as NOT_SUPPORTED still subscribes. Could a TRACK_INFO query do the same: on a NOT_SUPPORTED TRACK_STATUS, learn the track from a SUBSCRIBE instead of failing?

(Written with Claude Opus 5.5)

Activity

  1. coderabbitai commented on Oct 30, 2026

    @coderabbitai
    Contributor
    🔗 Related PRs

    #7187 - fix(net): subscribe blind when moq-transport discovery cannot prove absence [open]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. michaelstuurman commented on Oct 31, 2026

    @michaelstuurman
    ContributorAuthor

    Same dead end with moqx (the relay, not moqxr) on draft 18 as moq-relay's upstream, with a different refusal: REQUEST_ERROR 0xFFFFFFFF, which is moxygen's internal CANCELLED ("peer closed stream before reply"). moqx sent it after a moq-dev publisher behind it reset the stream: moxygen FINs right after TRACK_STATUS, and the draft-18 publisher takes the FIN as a withdrawal; that part is #7438.

    Two corrections to the issue above:

    (Written with Claude Opus 5.5)

  3. kixelated commented on Oct 31, 2026

    @kixelated
    Collaborator

    I mean, how much of this is a moqx bug? It's really not hard to implement TRACK_STATUS

  4. added
    questBeing tracked/planned in a quest. See `quest/`
    on Oct 31, 2026
  5. kixelated commented on Oct 31, 2026

    @kixelated
    Collaborator

    Closing as won't fix (maintainer decision, 2026-10-31). A moq-lite TRACK_INFO behind a moq-transport publisher still needs that publisher to answer TRACK_STATUS. Falling back to a SUBSCRIBE to learn the track is the kind of guessing rejected on moq-dev/moq#7187, so the fix belongs in the publisher: moqxr should implement TRACK_STATUS. The moqx failure in the follow-up comment was #7438, which is planned in moq-dev/moq#7441. That quest also fixes the stale doc/concept/standard.md sentence you found.

    (Written by Claude Opus 5.5)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questBeing tracked/planned in a quest. See `quest/`

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions