Skip to content

Flesh out the ICE Controllers interface section. - #118

Merged
pthatcher merged 1 commit into
w3c:mainfrom
Philipel-WebRTC:flesh-out-ice-controllers
Jun 2, 2026
Merged

Flesh out the ICE Controllers interface section.#118
pthatcher merged 1 commit into
w3c:mainfrom
Philipel-WebRTC:flesh-out-ice-controllers

Conversation

@Philipel-WebRTC

@Philipel-WebRTC Philipel-WebRTC commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator

Comment thread api-outline.md
undefined SetIceServers(sequence<IceServer> servers);

undefined gatherCandidates();
undefined gatherCandidates(sequence<IceServer> servers);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this gather new host candidates or reuse the existing ones? Should we allow that level of control? Do local candidates get gathered automatically before calling this?

Comment thread index.bs
4. Let |numInterfaces| be the [=list/size=] of |availableInterfaces|.
5. For each |interface| in |availableInterfaces|:
1. Run the following steps in parallel:
1. Send a STUN Binding request to the STUN server defined by |iceServer|, utilizing a local port allocated for host candidates on |interface|.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if there isn't one yet?

Comment thread index.bs
5. For each |interface| in |availableInterfaces|:
1. Run the following steps in parallel:
1. Send a STUN Binding request to the STUN server defined by |iceServer|, utilizing a local port allocated for host candidates on |interface|.
2. Wait for a successful STUN Binding response, for the request to time out after 30 seconds, or for |interface| to become unavailable.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure this is the right place to specify the duration of the timeout.

Comment thread index.bs



ISSUE: The network cost per network type needs to be defined.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to do that in the W3C or IETF?

Comment thread index.bs

ISSUE: What policies should be considered in relation to candidate discovery?

ISSUE: What are reasonable timeout limits? Implementation defined?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again, perhaps an IETF rather than IC3 thing

@pthatcher
pthatcher merged commit 0090e25 into w3c:main Jun 2, 2026
1 of 2 checks passed
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

Successfully merging this pull request may close these issues.

2 participants