Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the state of a connection with only administratively prohibited candidates? #2879

Open
alvestrand opened this issue Jun 12, 2023 · 1 comment

Comments

@alvestrand
Copy link
Contributor

This came up in connection with a situation where MDNS is blocked, but may have wider relevance.

The spec says:

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] block bad port list, and MAY choose to prohibit connections to other addresses.

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

@fippo
Copy link
Contributor

fippo commented Jun 12, 2023

I'd say new. If you can't resolve the host name of the mdns candidate you can't form a pair.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants