Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Editorial changes #646

Merged
merged 6 commits into from
Jan 16, 2025
Merged

Editorial changes #646

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
e2a3926
Editorial changes
martinduke Jan 10, 2025
4afd869
Update draft-ietf-moq-transport.md
martinduke Jan 16, 2025
71d1100
Update draft-ietf-moq-transport.md
martinduke Jan 16, 2025
368aa33
Merge branch 'main' into cleanup2
ianswett Jan 16, 2025
1c64f52
Merge branch 'main' into cleanup2
ianswett Jan 16, 2025
4095e57
Merge branch 'main' into cleanup2
gloinul Jan 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Editorial changes
  • Loading branch information
@martinduke
martinduke committed Jan 10, 2025
commit e2a3926622ba71c3efdd0404506586d184137d18
21 changes: 10 additions & 11 deletions draft-ietf-moq-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -827,16 +827,15 @@ to the old relay can be stopped with an UNSUBSCRIBE.

Publishing through the relay starts with publisher sending ANNOUNCE
control message with a `Track Namespace` ({{model-track}}).
The announce enables the relay to know which publisher to forward a
SUBSCRIBE to.
The ANNOUNCE enables the relay to know which publisher to forward a
SUBSCRIBE to, if the track name belongs to the namespace indicated in
the ANNOUNCE.
martinduke marked this conversation as resolved.
Show resolved Hide resolved

Relays MUST ensure that publishers are authorized by:

- Verifying that the publisher is authorized to publish the content
associated with the set of tracks whose Track Namespace matches the
announced namespace. Where the authorization and identification of
the publisher occurs depends on the way the relay is managed and
is application specific.
Relays MUST ensure that publishers are authorized by verifying that the
publisher is authorized to publish the content associated with the set of
martinduke marked this conversation as resolved.
Show resolved Hide resolved
tracks whose Track Namespace matches the announced namespace. Where the
authorization and identification of the publisher occurs depends on the way the
relay is managed and is application specific.

Relays respond with an ANNOUNCE_OK or ANNOUNCE_ERROR control message
providing the result of announcement. The entity receiving the
Expand All @@ -846,7 +845,7 @@ either ANNOUNCE_OK or ANNOUNCE_ERROR.
A Relay can receive announcements from multiple publishers for the same
Track Namespace and it SHOULD respond with the same response to each of the
publishers, as though it was responding to an ANNOUNCE
from a single publisher for a given tracknamespace.
from a single publisher for a given track namespace.

When a publisher wants to stop
new subscriptions for an announced namespace it sends an UNANNOUNCE.
Expand All @@ -866,7 +865,7 @@ publisher that has announced the subscription's namespace, unless it
already has an active subscription for the Objects requested by the
incoming SUBSCRIBE request from all available publishers.

When a relay receives an incoming ANNOUCE for a given namespace, for
When a relay receives an incoming ANNOUNCE for a given namespace, for
each active upstream subscription that matches that namespace, it SHOULD send a
SUBSCRIBE to the publisher that sent the ANNOUNCE.

Expand Down
Loading