Merge branch 'main' into message-split

draft-ietf-moq-transport.md

@@ -6,10 +6,18 @@ date: {DATE}
 category: std
 
 ipr: trust200902
-area: Applications and Real-Time
+area:  "Web and Internet Transport"
 submissionType: IETF
-workgroup: MOQ
-keyword: Internet-Draft
+workgroup: "Media Over QUIC"
+keyword:
+ - media over quic
+venue:
+  group: "Media Over QUIC"
+  type: "Working Group"
+  mail: "moq@ietf.org"
+  arch: "https://mailarchive.ietf.org/arch/browse/moq/"
+  github: "moq-wg/moq-transport"
+  latest: "https://moq-wg.github.io/moq-transport/draft-ietf-moq-transport.html"
 
 stand_alone: yes
 smart_quotes: no
@@ -717,11 +725,9 @@ the session that sent ANNOUNCE namespace=foobar.
 OBJECT message headers carry a short hop-by-hop `Track Alias` that maps to
 the Full Track Name (see {{message-subscribe-ok}}). Relays use the
 `Track Alias` of an incoming OBJECT message to identify its track and find
-the active subscribers for that track. Relays MUST NOT depend on OBJECT
-payload content for making forwarding decisions and MUST only depend on the
-fields, such as priority order and other metadata properties in the
-OBJECT message header. Unless determined by congestion response, Relays
-MUST forward the OBJECT message to the matching subscribers.
+the active subscribers for that track. Relays MUST forward OBJECT messages to
+matching subscribers in accordance to each subscription's priority, group order,
+and delivery timeout.
 
 ## Relay Object Handling