- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Jun 2023 12:49:27 +0000
- To: public-webrtc-logs@w3.org
alvestrand has just created a new issue for https://github.com/w3c/webrtc-pc: == What is the state of a connection with only administratively prohibited candidates? == This came up in connection with a situation where MDNS is blocked, but may have wider relevance. The spec says: <blockquote> A candidate is administratively prohibited if the UA has decided not to allow connection attempts to this address. For privacy reasons, there is no indication to the developer about whether or not an address/port is blocked; it behaves exactly as if there was no response from the address. The UA MUST prohibit connections to addresses on the [[Fetch](https://w3c.github.io/webrtc-pc/#bib-fetch)] [block bad port](https://fetch.spec.whatwg.org/#block-bad-port) list, and MAY choose to prohibit connections to other addresses. </blockquote> If all candidates are administratively prohibited, what is the state of the connection? New or Connecting? Does it ever go to Failed state? (At the moment, I think it remains in New state) Chromium bug: https://crbug.com/1447957 Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2879 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 12 June 2023 12:49:29 UTC