Skip to content

moq-lite-06: a repeated SETUP parameter or a second Setup Stream does not close the session #5521

Closed

Description

@kixelated

Found by the new moq-lite conformance lane in moq-dev/smoke, which drives moq 0.14.4 (crates.io) through moq-contribution-interop-runner at ae0364d. Both rows fail on native QUIC and WebTransport. Neither is covered by #5257, #5258 or #5259.

A repeated SETUP Parameter ID (L06-7-3-MUST-112)

Draft: a receiver closes the session with PROTOCOL_VIOLATION when a SETUP repeats a Parameter ID.

The runner, acting as the server, sends a SETUP that carries Cost (0x4) twice with the same value. The CLI logs WARN moq_net::lite::message: decode failed e=duplicate and keeps the session open until the runner gives up.

A second Setup Stream (L06-6-3-1-MUST-092)

Draft (drafts/draft-lcurley-moq-lite.md): "There is exactly one Setup Stream per direction; an endpoint that receives a second Setup Stream MUST close the session with a PROTOCOL_VIOLATION."

The runner opens a second unidirectional Setup Stream with an empty SETUP and FIN. The CLI logs received peer setup twice and keeps the session open:

DEBUG moq_net::lite::subscriber: received peer setup setup=Setup { probe: None, path: None, role: None, cost: None, hop: None }
DEBUG moq_net::lite::subscriber: received peer setup setup=Setup { probe: None, path: None, role: None, cost: None, hop: None }

Expected

Both close the session with PROTOCOL_VIOLATION (0x3). These look like they fit the quest/m1/lite-malformed-close.md rule that peer violations on control streams close the session.

Reproduce

From moq-dev/smoke: MOQ_BIN=$(command -v moq) just conformance, or from the runner checkout:

MOQ_CLI_BIN=$(command -v moq) bash tests/e2e/driven-moq-lite.sh native_quic build/moq-interop-runner l06-setup-duplicate-parameter l06-setup-duplicate-stream

(Written by Claude Opus 5.5)

Activity

  1. added
    questBeing tracked/planned in a quest. See `quest/`
    on Oct 15, 2026
  2. kixelated commented on Oct 16, 2026

    @kixelated
    CollaboratorAuthor

    Fixed on release by #5661 (backport of #4704's SETUP handling): a repeated SETUP parameter or a second Setup Stream now closes the session with PROTOCOL_VIOLATION, covered by repeated_setup_parameter_closes_the_session and accepted_lite_setup_refuses_a_second_setup_stream. main already had the fix via #4704. Closing by hand since release isn't the default branch.

    (Written by 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