From cbf39f884ecbb3c1d1da557cc589bcd5d59797a3 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Fri, 30 Oct 2026 04:59:07 -0700 Subject: [PATCH 1/2] chore(quest): claim quest/m2/relay-peer-addr.md Quest-Claim: cad4f7f171dee46c From e091eaafbdcc078c4edad42509044a712b5e1406 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Fri, 30 Oct 2026 05:00:25 -0700 Subject: [PATCH 2/2] quest: drop relay-peer-addr, already shipped as ConnectInfo (#6430) Co-Authored-By: Claude Opus 5.5 --- quest/m2/README.md | 1 - quest/m2/relay-peer-addr.md | 16 ---------------- 2 files changed, 17 deletions(-) delete mode 100644 quest/m2/relay-peer-addr.md diff --git a/quest/m2/README.md b/quest/m2/README.md index 4f4f2452b0a..c09b4358531 100644 --- a/quest/m2/README.md +++ b/quest/m2/README.md @@ -225,7 +225,6 @@ lite-07; bitrate enforcement is not part of this release. - [Task supervision](/quest/m2/task-supervision.md) - the auth decider loop, stats publisher, and moq-tokio's token and WebSocket internals are supervised like #5447's tasks - [Auth serve bound address](/quest/m2/auth-serve-bound-addr.md) - `moq auth serve` logs the port it actually bound -- [Relay exposes a verified peer address](/quest/m2/relay-peer-addr.md) - WebRTC and other embedded routes know the client's socket address - [RTMP client reports a publish or play error](/quest/m2/rtmp-client-error.md) - a refused publish or play surfaces its reason - [H.264 parsing with maintained crates](/quest/m2/h264-reader.md) - moq-mux parses SPS VUI with h264-reader and shares one bit reader across codec config parsers - [avcC and hvcC through mp4-atom](/quest/m2/mp4-atom-config.md) - moq-mux stops hand-writing the decoder config records its mp4-atom dependency already parses diff --git a/quest/m2/relay-peer-addr.md b/quest/m2/relay-peer-addr.md deleted file mode 100644 index d4886d5a653..00000000000 --- a/quest/m2/relay-peer-addr.md +++ /dev/null @@ -1,16 +0,0 @@ -# [S] Relay exposes a verified peer address - -## Goal - -An embedder of moq-relay's routes, including WebRTC (WHIP/WHEP), can read the -verified socket address of the client behind each session, never a forwarded -header. Today `listener::Peer` is crate-private and moq-rtc exposes no remote -address, while native QUIC already offers `remote_addr()`. - -## Plan - -Open question for the maintainer: the API shape (a request extension, a -field on the session, or a getter beside `remote_addr()`). Recommendation: a -public request extension, mirroring `MtlsPeer`, which embedded routes already -extract for the client certificate; it needs no change to the session types. -Keep it to one accessor that every transport fills.