Revert of Change initial DTLS retransmission timer from 1 second to 50ms.

Revert of Change initial DTLS retransmission timer from 1 second to 50ms. (patchset #2 id:20001 of https://codereview.webrtc.org/1981463002/ )

Reason for revert:
Seems like this CL cause
DtlsTransportChannelTest.TestReceiveClientHelloBeforeRemoteFingerprint
DtlsTransportChannelTest.TestReceiveClientHelloBeforeWritable
to consistently fail on Win DrMemory Full and for
DtlsTransportChannelTest.TestReceiveClientHelloBeforeRemoteFingerprint
DtlsTransportChannelTest.TestReceiveClientHelloBeforeWritable
to consistently fail on Linux Memcheck

Original issue's description:
> Change initial DTLS retransmission timer from 1 second to 50ms.
>
> This will help ensure a timely DTLS handshake when there's packet
> loss. It will likely result in spurious retransmissions (since the
> RTT is usually > 50ms), but since exponential backoff is still used,
> there will at most be ~4 extra retransmissions. For a time-sensitive
> application like WebRTC this seems like a reasonable tradeoff.
>
> R=juberti@chromium.org, juberti@webrtc.org, pthatcher@webrtc.org
>
> Committed: https://crrev.com/1e435628366fb9fed71632369f05928ed857d8ef
> Cr-Commit-Position: refs/heads/master@{#12853}

TBR=pthatcher@webrtc.org,juberti@webrtc.org,juberti@chromium.org,deadbeef@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true

Committed: https://crrev.com/49c0869825c4c6165d64afc1002d40ecb68240e5
Cr-Commit-Position: refs/heads/master@{#12864}

[philipel, 2016-05-24 08:49:30]

Created Revert of Change initial DTLS retransmission timer from 1 second to
50ms.

[commit-bot: I haz the power, 2016-05-24 08:49:34]

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

[commit-bot: I haz the power, 2016-05-24 08:49:45]

Description was changed from

==========
Revert of Change initial DTLS retransmission timer from 1 second to 50ms.
(patchset #2 id:20001 of https://codereview.webrtc.org/1981463002/ )

Reason for revert:
Seems like this CL cause
DtlsTransportChannelTest.TestReceiveClientHelloBeforeRemoteFingerprint
DtlsTransportChannelTest.TestReceiveClientHelloBeforeWritable
to consistently fail on Win DrMemory Full and for
DtlsTransportChannelTest.TestReceiveClientHelloBeforeRemoteFingerprint
DtlsTransportChannelTest.TestReceiveClientHelloBeforeWritable
to consistently fail on Linux Memcheck

Original issue's description:
> Change initial DTLS retransmission timer from 1 second to 50ms.
> 
> This will help ensure a timely DTLS handshake when there's packet
> loss. It will likely result in spurious retransmissions (since the
> RTT is usually > 50ms), but since exponential backoff is still used,
> there will at most be ~4 extra retransmissions. For a time-sensitive
> application like WebRTC this seems like a reasonable tradeoff.
> 
> R=juberti@chromium.org, juberti@webrtc.org, pthatcher@webrtc.org
> 
> Committed: https://crrev.com/1e435628366fb9fed71632369f05928ed857d8ef
> Cr-Commit-Position: refs/heads/master@{#12853}

TBR=pthatcher@webrtc.org,juberti@webrtc.org,juberti@chromium.org,deadbeef@web...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
==========

to

==========
Revert of Change initial DTLS retransmission timer from 1 second to 50ms.
(patchset #2 id:20001 of https://codereview.webrtc.org/1981463002/ )

Reason for revert:
Seems like this CL cause
DtlsTransportChannelTest.TestReceiveClientHelloBeforeRemoteFingerprint
DtlsTransportChannelTest.TestReceiveClientHelloBeforeWritable
to consistently fail on Win DrMemory Full and for
DtlsTransportChannelTest.TestReceiveClientHelloBeforeRemoteFingerprint
DtlsTransportChannelTest.TestReceiveClientHelloBeforeWritable
to consistently fail on Linux Memcheck

Original issue's description:
> Change initial DTLS retransmission timer from 1 second to 50ms.
> 
> This will help ensure a timely DTLS handshake when there's packet
> loss. It will likely result in spurious retransmissions (since the
> RTT is usually > 50ms), but since exponential backoff is still used,
> there will at most be ~4 extra retransmissions. For a time-sensitive
> application like WebRTC this seems like a reasonable tradeoff.
> 
> R=juberti@chromium.org, juberti@webrtc.org, pthatcher@webrtc.org
> 
> Committed: https://crrev.com/1e435628366fb9fed71632369f05928ed857d8ef
> Cr-Commit-Position: refs/heads/master@{#12853}

TBR=pthatcher@webrtc.org,juberti@webrtc.org,juberti@chromium.org,deadbeef@web...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
==========

[commit-bot: I haz the power, 2016-05-24 08:49:46]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-24 08:49:54]

Description was changed from

==========
Revert of Change initial DTLS retransmission timer from 1 second to 50ms.
(patchset #2 id:20001 of https://codereview.webrtc.org/1981463002/ )

Reason for revert:
Seems like this CL cause
DtlsTransportChannelTest.TestReceiveClientHelloBeforeRemoteFingerprint
DtlsTransportChannelTest.TestReceiveClientHelloBeforeWritable
to consistently fail on Win DrMemory Full and for
DtlsTransportChannelTest.TestReceiveClientHelloBeforeRemoteFingerprint
DtlsTransportChannelTest.TestReceiveClientHelloBeforeWritable
to consistently fail on Linux Memcheck

Original issue's description:
> Change initial DTLS retransmission timer from 1 second to 50ms.
> 
> This will help ensure a timely DTLS handshake when there's packet
> loss. It will likely result in spurious retransmissions (since the
> RTT is usually > 50ms), but since exponential backoff is still used,
> there will at most be ~4 extra retransmissions. For a time-sensitive
> application like WebRTC this seems like a reasonable tradeoff.
> 
> R=juberti@chromium.org, juberti@webrtc.org, pthatcher@webrtc.org
> 
> Committed: https://crrev.com/1e435628366fb9fed71632369f05928ed857d8ef
> Cr-Commit-Position: refs/heads/master@{#12853}

TBR=pthatcher@webrtc.org,juberti@webrtc.org,juberti@chromium.org,deadbeef@web...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
==========

to

==========
Revert of Change initial DTLS retransmission timer from 1 second to 50ms.
(patchset #2 id:20001 of https://codereview.webrtc.org/1981463002/ )

Reason for revert:
Seems like this CL cause
DtlsTransportChannelTest.TestReceiveClientHelloBeforeRemoteFingerprint
DtlsTransportChannelTest.TestReceiveClientHelloBeforeWritable
to consistently fail on Win DrMemory Full and for
DtlsTransportChannelTest.TestReceiveClientHelloBeforeRemoteFingerprint
DtlsTransportChannelTest.TestReceiveClientHelloBeforeWritable
to consistently fail on Linux Memcheck

Original issue's description:
> Change initial DTLS retransmission timer from 1 second to 50ms.
>
> This will help ensure a timely DTLS handshake when there's packet
> loss. It will likely result in spurious retransmissions (since the
> RTT is usually > 50ms), but since exponential backoff is still used,
> there will at most be ~4 extra retransmissions. For a time-sensitive
> application like WebRTC this seems like a reasonable tradeoff.
>
> R=juberti@chromium.org, juberti@webrtc.org, pthatcher@webrtc.org
>
> Committed: https://crrev.com/1e435628366fb9fed71632369f05928ed857d8ef
> Cr-Commit-Position: refs/heads/master@{#12853}

TBR=pthatcher@webrtc.org,juberti@webrtc.org,juberti@chromium.org,deadbeef@web...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true

Committed: https://crrev.com/49c0869825c4c6165d64afc1002d40ecb68240e5
Cr-Commit-Position: refs/heads/master@{#12864}
==========

[commit-bot: I haz the power, 2016-05-24 08:49:55]

Patchset 1 (id:??) landed as
https://crrev.com/49c0869825c4c6165d64afc1002d40ecb68240e5
Cr-Commit-Position: refs/heads/master@{#12864}