Remove time constraint on first retransmit of a packet.

Remove time constraint on first retransmit of a packet.

We don't allow more than one retransmission within one RTT, but the RTT
estimate might be off. Reasonably, the remote end will not send a NACK
until the packet after has been received - so always resend on first
request.

Committed: https://crrev.com/affa39cb39c77408109fef691533021533d969e1
Cr-Commit-Position: refs/heads/master@{#10362}

[sprang_webrtc, 2015-10-19 13:54:15]

sprang@webrtc.org changed reviewers:
+ stefan@webrtc.org

[stefan-webrtc, 2015-10-21 14:13:43]

lgtm

[sprang_webrtc, 2015-10-21 14:58:17]

The CQ bit was checked by sprang@webrtc.org

[commit-bot: I haz the power, 2015-10-21 14:58:28]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1414563003/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1414563003/20001

[commit-bot: I haz the power, 2015-10-21 16:58:39]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-10-21 16:58:40]

Try jobs failed on following builders:
  android_arm64_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL)
  android_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL)
  android_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL)

[sprang_webrtc, 2015-10-21 20:45:19]

The CQ bit was checked by sprang@webrtc.org

[commit-bot: I haz the power, 2015-10-21 20:45:29]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1414563003/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1414563003/20001

[commit-bot: I haz the power, 2015-10-21 20:46:37]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-10-21 20:46:51]

Patchset 2 (id:??) landed as
https://crrev.com/affa39cb39c77408109fef691533021533d969e1
Cr-Commit-Position: refs/heads/master@{#10362}