IETF MOQ WG: Call for agenda items: Seattle In-person meeting - MoqT URI
Cullen Fluffy Jennings posted to the MOQ working group mailing list on September 20, 2026. I’d like time to discuss “MoQT URI”. Probably 30 to 60 minutes. I’d like to talk about a few things: 1. moving the URI specifica…
Message Snapshot
- List:
moq@ietf.org - Thread subject: Call for agenda items: Seattle In-person meeting - MoqT URI
- Message subject: [Moq] Re: Call for agenda items: Seattle In-person meeting - MoqT URI
- Author: Cullen Fluffy Jennings
- Published: 2026-09-20T19:23:07.000Z
- Source tag:
ietf-mailing-list - Message URL: Open in IETF Mail Archive
Summary
Cullen Fluffy Jennings posted to the MOQ working group mailing list on September 20, 2026. I’d like time to discuss “MoQT URI”. Probably 30 to 60 minutes. I’d like to talk about a few things: 1. moving the URI specifica…
Why It Matters
This message came from the public MOQ working group archive and captures active discussion, meeting coordination, or implementation feedback around Media over QUIC.
Message Excerpt
I’d like time to discuss “MoQT URI”. Probably 30 to 60 minutes. I’d like to talk about a few things: 1. moving the URI specification, DNS resolution, and TLS certificate matching to a separate draft.
Plain-Text Body
I’d like time to discuss “MoQT URI”. Probably 30 to 60 minutes.
I’d like to talk about a few things:
-
moving the URI specification, DNS resolution, and TLS certificate matching to a separate draft.
-
issues when using raw quic
-
issues when using WebTransport
-
the way we are using fragments
-
mDNS for local relays and use cases like google cast / airplay