Skip to content

Updates for SUBSCRIBE_NAMESPACE and SUBSCRIBE_TRACKS - #5

Open
sharmafb wants to merge 1 commit into
afrind:mainfrom
sharmafb:patch-2
Open

sharmafb wants to merge 1 commit into
afrind:mainfrom
sharmafb:patch-2

Conversation

@sharmafb

Copy link
Copy Markdown
Contributor

This is a part of the work to make moq-test up-to-date with the most recent version of the MoQ specification.

This is a part of the work to make moq-test up-to-date with the most recent version of the MoQ specification.
@sharmafb
sharmafb requested a review from afrind as a code owner June 22, 2026 21:16
Comment thread draft-afrind-moq-test.md
Upon receiving a SUBSCRIBE_ANNOUNCES with a Track Namespace, the publisher MUST
use PUBLISH to send objects according to the parameters of the namespace. If the
publisher receives a PUBLISH_ERROR, it will stop sending objects immediately.
Upon receiving SUBSCRIBE_NAMESPACE with a complete moq-test Track Namespace as

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the purpose of supporting SUB_NS? Primarily only relays need to handle that message.

Comment thread draft-afrind-moq-test.md
Namespace Suffix, indicating the subscribed prefix is itself the matching
namespace. The publisher MUST NOT send PUBLISH messages.

Upon receiving SUBSCRIBE_TRACKS with a complete moq-test Track Namespace as the

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we expect the subscriber to close the SUBSCRIBE_TRACKS after completion?

Should we fail SUB_TRACKS if the namespace doesn't name a full moq-test namespace?

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants