- From: shushushu via GitHub <noreply@w3.org>
- Date: Tue, 19 May 2026 07:23:50 +0000
- To: public-webrtc-logs@w3.org
> Streaming from a public media server is not a P2P use case, so seems irrelevant to the title of this issue. However, ICE can be considered as one way of getting a pair of IP addresses that may be able to connect; if QUIC were able to take in an IP address pair rather than what it currently does, these modules would be relatively independent. Fair point on the title — the client-server case isn't P2P. But your framing of ICE as "one way of getting an IP address pair" is exactly what I was trying to get at: ICE could be one producer of a usable address pair, and the transport format a consumer — without assuming the two are coupled. The public-server case is just the simplest example of that abstraction; the broader point is that ICE and the transport format seem separable. -- GitHub Notification of comment by shushushv Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/102#issuecomment-4485372810 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 May 2026 07:23:51 UTC