clarify order of sending unsubscribe

moq-wg · Sep 30, 2024 · b836962 · b836962
1 parent b6b7d56
commit b836962
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/draft-ietf-moq-transport.md b/draft-ietf-moq-transport.md
@@ -583,8 +583,8 @@ there are still open subscriptions on a connection.
 The GOAWAY message does not immediately impact subscription state. A subscriber
 SHOULD individually UNSUBSCRIBE for each existing subscription, while a
 publisher MAY reject new SUBSCRIBEs while in the draining state. When the server
-is a subscriber, it SHOULD send a GOAWAY message prior to any UNSUBSCRIBE
-messages.
+is a subscriber, it SHOULD send a GOAWAY message to downstream subscribers prior to any UNSUBSCRIBE
+messages to upstream publishers.
 
 After the client receives a GOAWAY, it's RECOMMENDED that the client waits until
 there are no more active subscriptions before closing the session with NO_ERROR.