IETF MOQ WG: URI Resolution for MOQT and TLS cert matching

Message Snapshot

• List: moq@ietf.org
• Thread subject: URI Resolution for MOQT and TLS cert matching
• Message subject: [Moq] Re: URI Resolution for MOQT and TLS cert matching
• Author: Magnus Westerlund
• Published: 2026-09-08T13:54:27.000Z
• Source tag: ietf-mailing-list
• Message URL: Open in IETF Mail Archive

Summary

Magnus Westerlund posted to the MOQ working group mailing list on September 8, 2026. Hi, That is a good answer. I tried looking into WebTrans spec and they didn’t appear to have addressed the discovery part things speci…

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

Hi, That is a good answer. I tried looking into WebTrans spec and they didn’t appear to have addressed the discovery part things specifically. However, I do think we will have to ensure that we don’t creates issues for normal HTTPS usages also. Thus, I was asking if we needed section 3.2.2 that appear to just repeat w…

Plain-Text Body

Hi,

That is a good answer. I tried looking into WebTrans spec and they didn’t appear to have addressed the discovery part things specifically. However, I do think we will have to ensure that we don’t creates issues for normal HTTPS usages also. Thus, I was asking if we needed section 3.2.2 that appear to just repeat what is specified in the SVCB RFC.

/Magnus

From: Cullen Fluffy Jennings fluffy@iii.ca Date: Tuesday, 8 September 2026 at 15:46 To: Magnus Westerlund magnus.westerlund@ericsson.com Cc: MOQ Mailing List moq@ietf.org Subject: Re: [Moq] URI Resolution for MOQT and TLS cert matching

Whatever we do, I am going to feel pretty strongly that we have to have at least one mandatory to implement path that provides modern security.

My read of the RFCs is that WebTransport does not do that largely because of the historic development of HTTP.