Allow applications to limit the ICE check rate through RTCConfiguration

webrtc/api/peerconnectioninterface.h

Index: webrtc/api/peerconnectioninterface.h
diff --git a/webrtc/api/peerconnectioninterface.h b/webrtc/api/peerconnectioninterface.h
index 0280c18dbdbf7f4c28efa6cff8fd49f60bee17b0..6cc8be7112b691f03409d06e0cdf4f4e4f913562 100644
--- a/webrtc/api/peerconnectioninterface.h
+++ b/webrtc/api/peerconnectioninterface.h
@@ -380,6 +380,9 @@ class PeerConnectionInterface : public rtc::RefCountInterface {
     // If true, ICE role is redetermined when peerconnection sets a local
     // transport description that indicates an ICE restart.
     bool redetermine_role_on_ice_restart = true;
+    // If set, the min interval (max rate) at which we will send ICE checks
+    // (STUN pings), in milliseconds.

[Taylor Brandstetter, 2017/02/02 07:03:55]

Nit: The variable could be named in milliseconds (ice_check_min_interval_ms) to
make this more clear

[skvlad, 2017/02/02 08:51:24]

None of the other timeout/interval parameters are. If you prefer clarity over
consistency, I can rename it.

[Taylor Brandstetter, 2017/02/02 18:16:01]

Nah, consistency is better.

+    rtc::Optional<int> ice_check_min_interval;
     //
     // Don't forget to update operator== if adding something.
     //