From f1c1215ac14d8be2c3326c455c0f760bb541de1d Mon Sep 17 00:00:00 2001 From: ianswett Date: Sun, 2 Mar 2025 14:04:37 -0500 Subject: [PATCH] Move Connection URL section into Session I'm not sure it says anything useful, and is somewhat confusing in my opinion, but moving it for now. --- draft-ietf-moq-transport.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/draft-ietf-moq-transport.md b/draft-ietf-moq-transport.md index 33223953..5341345e 100644 --- a/draft-ietf-moq-transport.md +++ b/draft-ietf-moq-transport.md @@ -434,13 +434,6 @@ the ones defined by HTTP ({{?RFC9110, Section 10}}); if, at a given moment in time, two tracks within the same scope contain different data, they have to have different names and/or namespaces. -### Connection URL - -Each track MAY have one or more associated connection URLs specifying -network hosts through which a track may be accessed. The syntax of the -Connection URL and the associated connection setup procedures are -specific to the underlying transport protocol usage {{session}}. - # Sessions {#session} @@ -493,6 +486,13 @@ PATH parameter ({{path}}) which is sent in the CLIENT_SETUP message at the start of the session. The ALPN value {{!RFC7301}} used by the protocol is `moq-00`. +### Connection URL + +Each track MAY have one or more associated connection URLs specifying +network hosts through which a track may be accessed. The syntax of the +Connection URL and the associated connection setup procedures are +specific to the underlying transport protocol usage {{session}}. + ## Version and Extension Negotiation {#version-negotiation} Endpoints use the exchange of Setup messages to negotiate the MOQT version and