Landing Recent QUIC changes until 7/16/2015 14:26 UTC.

Remove unused using declarations (using internal tool + manaual fixes).

relnote: n/a (metadata)

Merge internal change: 98399640
https://codereview.chromium.org/1242273006/

relnote: restore (again) unused method QuicStreamSequencer::MarkConsumed

Basically a rollback of internal change: 97716158

Merge internal change: 98352120
https://codereview.chromium.org/1239373002/

relnote: Deprecate FLAGS_quic_delay_retransmission_alarm.

Merge internal change: 98115538
https://codereview.chromium.org/1243763002/

relnote: Impose a max cwnd of 200 packets on QUIC connections, flag
protected by FLAGS_quic_limit_max_cwnd and blocked by b/22063985.

In preparation for Chrome advertising a 1MB receive window.

Enabled FLAGS_quic_limit_max_cwnd to true in chromium.

Merge internal change: 98115159
https://codereview.chromium.org/1241193003/

relnote:  Flag-protected by FLAGS_increase_time_wait_list; enabled by default.
Increase the default time-wait time for closed QUIC connections to 200
seconds. Increase quic_time_wait_list_max_connections to 600,000
connections.

This is a partial fix for b/21026951.

Merge internal change: 97975101
https://codereview.chromium.org/1245783002/

Change QUIC to use a max CWND based on 60% of the peer's receive buffer,
rather than 95%.  Protected by FLAGS_quic_use_conservative_receive_buffer.

Merge internal change: 97966998
https://codereview.chromium.org/1238423002/

relnote: QUIC bandwidth resumption: check higher in the stack that a
provided estimate is recent enough. No behavior change.

SendAlgorithmInterface::ResumeConnectionState now does what its name
suggests it will do. Verification of whether the estimate came from the
same serving region, or whether the estimate is reasonably recent, now
all happens in the same place; in QuicServerSession::OnConfigNegotiated.

This also means we can change the return type of ResumeConnectionState
from bool to void, and this ends up touching quite a few different files.

This is refactoring for b/22292065, in which we will be calling
ResumeConnectionState with a freshly constructed CachedNetworkParams
without a timestamp, and this avoid us having to worry about forging a
recent timestamp just to make the validity checks down in TcpCubicSender
pass.

Merge internal change: 97868683
https://codereview.chromium.org/1240363002/

relnote: Add new QUIC connection tags kIFW5, kIFW6, kIFW7 to enable finch
trial to study smaller initial receive flow control window in combination
with auto-tuning.

The default receive flow control window is large, 1MB.  With flow
control auto tuning, UMA histograms for BlockedFrames sent show little
difference whether auto-tuning is enabled.  The conjecture is that due
to the large default size, the BlockedFrames are largely due to
backend services not consuming data, rather than flow control window
constraining BDP.  This status quo favors performance, but at the cost
of wasted memory, and worse a potential memory denial of service threat.

The goal of this trial will be to see if auto-tuning allows relatively
small, on the order of 1/10th status quo size, initial window size can
be used without dramatically increasing the number of BlockedFrames.
If so, it would trade-off a little performance, amortizing to near
zero, in exchange for better DOS resistence.

Merge internal change: 97828377
https://codereview.chromium.org/1242803002/

R=rch@chromium.org

Review URL: https://codereview.chromium.org/1244903002

Cr-Commit-Position: refs/heads/master@{#339510}

0 files changed, 0 insertions, 0 deletions