Subject: [Ice] Confirming consensus on ICE-bis IETF 95 open issues

From: Ari Keränen <[email-masked]>
Date: Mon, 18 Apr 2016 11:25:38 +0000

WG,

At the IETF 95 meeting we reached the following conclusions regarding ICEbis (https://www.ietf.org/proceedings/95/slides/slides-95-ice-4.pdf). The purpose of this e-mail is to verify consensus on the list. If you have any questions or comments, please comment on the list as soon as possible.

Keep-alives (slide #3)
- Agreed to remove all text talking about keep-alives when the remote peer does not support ICE. That includes removing the reference to draft-ietf-avt-rtp-no-op.

Connectivity check pacing (slide #4)
Agreed to:
- Specify 5ms as the min Ta value.
- Specify that endpoints SHOULD use 50ms default Ta value.
- Remove the distinction between RTP and non-RTP. Endpoints are still allowed to use different values e.g. for low bandwidth protocols.

The agreed Ta values can be changed if new information is provided before the publication request is done.

Aggressive nomination (slide #5-6)
- It was agreed to adopt both alternatives presented in the slides:
  - Endpoints MUST only nominate one candidate pair, but MUST be able to receive multiple nominations in which case the candidate pair with the highest priority MUST be used.
  - Endpoints will include a new ice-option, indicating that aggressive nomination is not supported. The need to be able to receive multiple nominations (see above) is to be able to handle remote peers that don’t process ice-options properly.

Cheers,
Ari & Peter