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:11:04.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, I took a look at the draft. I do see the need to specify these information I think the main question is the scope and if we need a…

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, I took a look at the draft. I do see the need to specify these information I think the main question is the scope and if we need all of these from the start? I do wonder about the need to repeat what applies for WebTrans establishment. Would it not be sufficient to point to the relevant specifications?

Plain-Text Body

Hi,

I took a look at the draft. I do see the need to specify these information I think the main question is the scope and if we need all of these from the start?

I do wonder about the need to repeat what applies for WebTrans establishment. Would it not be sufficient to point to the relevant specifications?

I find it interesting to find the discussion of SRV and mDNS in this document. But, maybe there should be a bit more discussion about the actual usage that motivates this introduction.

I will have to think a bit more about the many options for the subjectAltName matching and if one can discern between the different type or there are a risk of mistaking one type for the other.

Cheers

Magnus

From: Cullen Fluffy Jennings fluffy@iii.ca Date: Saturday, 5 September 2026 at 18:22 To: MOQ Mailing List moq@ietf.org Subject: [Moq] URI Resolution for MOQT and TLS cert matching

Right now the MoQT draft is missing information on how to implement DNS resolution of URI and how the TLS certificate matches to the URI. After some discussion on https://github.com/moq-wg/moq-transport/issues/1839, it looks like an separate spec is probably the best way to resolve this. It will need review form the DNS and Certificate people and having it as a separate spec certainly makes that easier for them.

Suhas and I put together a draft for this at https://www.ietf.org/archive/id/draft-jennings-moq-discovery-01.html