Landing Recent QUIC changes until 2015-11-09 20:32 UTC

Landing Recent QUIC changes until 2015-11-09 20:32 UTC

Add client-side support of cert transparency for QUIC, gated at QUIC_VERSION_30.

With this change, when the negotiated version > QUIC_VERSION_29, the client indicates that it supports cert transparency in client hello, and caches the CSCT value if it exists in server's response. However, the client NEITHER demands SCT NOR verifies the received SCT (e.g., it is up to Chrome how to verify).
Merge internal change: 107397642
https://codereview.chromium.org/1435943002/

Not sending QUIC packets if the send alarm is set. Behind FLAGS_respect_send_alarm

This fixes a subtle bug where we weren't always respecting priorities when writing.

I posit that if we are send limited by the sent packet manager, we expect to
resume with OnCanWrite, and resume the highest priority session.  Unfortunately
right now that's not the case.  When the highest priority session gets blocked
by the sent packet manager it schedules the alarm. However it's perfectly
possible that before the alarm fires, we get an incoming request, process it,
that stream checks to see if it can write, and when CanWrite checks now(), we
are past the time when the alarm should have fired (due to doing a lot of work,
busy machine, what have you) and write data for the random stream.
Merge internal change: 107380116
https://codereview.chromium.org/1439653002/

Add token binding negotiation to QUIC

This adds a tag (TBKP) to the SCFG and CHLO messages containing a taglist as a value of the supported token binding key parameters (P256 is currently the only supported param). This replaces the TLS token binding negotiation extension as part of the broader Token Binding spec when done over QUIC.

Token binding negotiation is off by default - it must be turned on server-side in QuicCryptoServerConfig::ConfigOptions and client side in QuicCryptoClientConfig. If it is enabled, the application layer using QUIC must handle the rest of the Token Binding protocol.

More information (including links to the Token Binding specs) is in this doc: https://docs.google.com/document/d/12eKfkdC7g5IGUCtghzg7Wi__qiEkY65fX09n8sjLtHg/edit?pli=1#heading=h.y8fw05yhvdsg
Merge internal change: 107277639
https://codereview.chromium.org/1437893002/

Make comments for EndToEndTest.LargePostEarlyResponse more clear. Rearrange code to clarifying the logic when sending request header and body separately.
Merge internal change: 107261172
https://codereview.chromium.org/1433353002/

Further reduce the number of QUIC end-to-end test variations that we run from 54 to 30, by only running the version negotiation variants when either all or none of other options are enabled.

Among other things, this will help the perfomance of these test
in the Chrome memory bots.
Merge internal change: 107172676
https://codereview.chromium.org/1414953012/

Add some helper methods to QuicTestServer
Merge internal change: 107150707
https://codereview.chromium.org/1433813002/

Move the call to revive packets from QuicConnection::ProcessUdpPacket to QuicConnection::OnPacketComplete. This avoid hitting a DCHECK in the EndToEnd tests when: FEC is enabled, stateless rejects are enabled and packets are reordered.
Merge internal change: 107136813
https://codereview.chromium.org/1419303009/

Reduce the number of QUIC end-to-end test combinations that are from from 240 to 46, by looking at five of the options, and only running when either none of them, all of them or just one of them is enabled.
Merge internal change: 107135565
https://codereview.chromium.org/1418503022/

Clean up "magic" constants in QuicFramerTest to add comments which explains their values and extract out to named constants.
Merge internal change: 107036345
https://codereview.chromium.org/1435673002/

Replace QuicEncryptedPacket argument in QuicConnectionDebugVisitor::OnPacketSent with an encrypted length. No functional change.
Merge internal change: 107034442
https://codereview.chromium.org/1433783004/

Override ReliableQuicStream::StopReading() to send RST_STREAM+NO_ERROR if CloseWriteSide() is called before StopReading().

Currently we always call StopReading() before calling CloseWriteSide(). However, there is not restriction to prevent calling StopReading() after CloseWrite(), in which case we should also send a QUIC_STREAM_NO_ERROR rst to stop the peer to sending more data. This feature improves RST_STREAM+NO_ERROR mechanism to be more future-proof.
Merge internal change: 106990301
https://codereview.chromium.org/1433063002/

Update the comment of --quic_version.
Merge internal change: 106978852
https://codereview.chromium.org/1425823005/

Pass in connection ID and supported version to  QuicFramer::BuildVersionNegotiationPacket, instead of passing in a QuicPacketHeader and supported versions.
Merge internal change: 106955386
https://codereview.chromium.org/1433703005/

Change bufferring data structure for QuicStreamSequencer. Protected by FLAGS_quic_use_stream_sequencer_buffer.
Swith QuicStreamSequencer's underlying data structure from QuicFrameList to StreamSequencerBuffer.
Merge internal change: 106947577
https://codereview.chromium.org/1433793002/

Add include to reflect what is already used.
Merge internal change: 106946658
https://codereview.chromium.org/1433013003/

Add a data structure QuicMultipathTransmissionsMap which is not in use now.
QuicMultipathTransmissionsMap manages packets which are transmitted across multiple paths. Also add a new struct QuicPathIdPacketNumber which comprises both QuicPathId and QuicPacketNumber.
Merge internal change: 106938391
https://codereview.chromium.org/1431363002/

Earlier check for nullptr.
Merge internal change: 106859834
https://codereview.chromium.org/1433783003/

Quic streams honor RST_STREAM + NO_ERROR on the write side.

Override QuicDataStream CloseWriteSide method to honor QUIC_STREAM_NO_ERROR on QUIC_VERSION_29 or later versions: send rst stream when writing to a stream initiated by the peer is finished but incoming data hasn't been received completely.
Merge internal change: 106853342
https://codereview.chromium.org/1413373013/

Add OnConnectionMigration method to QuicSentPacketManager. Add OnConnectionMigration interface to SendAlgorithmInterface and RttStats. No functional change expected.

This change is preparing to reset cwnd and rtt measurement when the client migrates to a different network.
Merge internal change: 106851267
https://codereview.chromium.org/1435553004/

Factoring a QuicCryptoServerStreamBase API out of QuicCryptoServerStream
Merge internal change: 106845785
https://codereview.chromium.org/1413613016/

Deprecate --gfe2_reloadable_flag_quic_stop_checking_for_mismatch_ids
Merge internal change: 106845547
https://codereview.chromium.org/1418963008/

No functional change.  Minor change to reorder when the list of QuicAckListeners is swapped into the TransmissionInfo in order to avoid an extra allocation.
Merge internal change: 106814823
https://codereview.chromium.org/1428303003/

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

[rjshade, 2015-11-11 20:40:07]

Description was changed from

==========
Add client-side support of cert transparency for QUIC, gated at QUIC_VERSION_30.

With this change, when the negotiated version > QUIC_VERSION_29, the client
indicates that it supports cert transparency in client hello, and caches the
CSCT value if it exists in server's response. However, the client NEITHER
demands SCT NOR verifies the received SCT (e.g., it is up to Chrome how to
verify).
Merge internal change: 107397642




Not sending QUIC packets if the send alarm is set. Behind
FLAGS_respect_send_alarm

This fixes a subtle bug where we weren't always respecting priorities when
writing.

I posit that if we are send limited by the sent packet manager, we expect to
resume with OnCanWrite, and resume the highest priority session.  Unfortunately
right now that's not the case.  When the highest priority session gets blocked
by the sent packet manager it schedules the alarm. However it's perfectly
possible that before the alarm fires, we get an incoming request, process it,
that stream checks to see if it can write, and when CanWrite checks now(), we
are past the time when the alarm should have fired (due to doing a lot of work,
busy machine, what have you) and write data for the random stream.
Merge internal change: 107380116



Add token binding negotiation to QUIC

This adds a tag (TBKP) to the SCFG and CHLO messages containing a taglist as a
value of the supported token binding key parameters (P256 is currently the only
supported param). This replaces the TLS token binding negotiation extension as
part of the broader Token Binding spec when done over QUIC.

Token binding negotiation is off by default - it must be turned on server-side
in QuicCryptoServerConfig::ConfigOptions and client side in
QuicCryptoClientConfig. If it is enabled, the application layer using QUIC must
handle the rest of the Token Binding protocol.

More information (including links to the Token Binding specs) is in this doc:
https://docs.google.com/document/d/12eKfkdC7g5IGUCtghzg7Wi__qiEkY65fX09n8sjLt...
Merge internal change: 107277639



Make comments for EndToEndTest.LargePostEarlyResponse more clear. Rearrange code
to clarifying the logic when sending request header and body separately.
Merge internal change: 107261172



Further reduce the number of QUIC end-to-end test variations that we run from 54
to 30, by only running the version negotiation variants when either all or none
of other options are enabled.

Among other things, this will help the perfomance of these test
in the Chrome memory bots.
Merge internal change: 107172676



Add some helper methods to QuicTestServer
Merge internal change: 107150707



Move the call to revive packets from QuicConnection::ProcessUdpPacket to
QuicConnection::OnPacketComplete. This avoid hitting a DCHECK in the EndToEnd
tests when: FEC is enabled, stateless rejects are enabled and packets are
reordered.
Merge internal change: 107136813



Reduce the number of QUIC end-to-end test combinations that are from from 240 to
46, by looking at five of the options, and only running when either none of
them, all of them or just one of them is enabled.
Merge internal change: 107135565



Add static MovePackets method to QUIC crypto_test_utils
Merge internal change: 107067016



Clean up "magic" constants in QuicFramerTest to add comments which explains
their values and extract out to named constants.
Merge internal change: 107036345




Replace QuicEncryptedPacket argument in QuicConnectionDebugVisitor::OnPacketSent
with an encrypted length. No functional change.
Merge internal change: 107034442




Override ReliableQuicStream::StopReading() to send RST_STREAM+NO_ERROR if
CloseWriteSide() is called before StopReading().

Currently we always call StopReading() before calling CloseWriteSide(). However,
there is not restriction to prevent calling StopReading() after CloseWrite(), in
which case we should also send a QUIC_STREAM_NO_ERROR rst to stop the peer to
sending more data. This feature improves RST_STREAM+NO_ERROR mechanism to be
more future-proof.
Merge internal change: 106990301




Update the comment of --quic_version.
Merge internal change: 106978852




Pass in connection ID and supported version to 
QuicFramer::BuildVersionNegotiationPacket, instead of passing in a
QuicPacketHeader and supported versions.
Merge internal change: 106955386




Change bufferring data structure for QuicStreamSequencer. Protected by
FLAGS_quic_use_stream_sequencer_buffer.
Swith QuicStreamSequencer's underlying data structure from QuicFrameList to
StreamSequencerBuffer.
Merge internal change: 106947577




Add include to reflect what is already used.
Merge internal change: 106946658



Add a data structure QuicMultipathTransmissionsMap which is not in use now.
QuicMultipathTransmissionsMap manages packets which are transmitted across
multiple paths. Also add a new struct QuicPathIdPacketNumber which comprises
both QuicPathId and QuicPacketNumber.
Merge internal change: 106938391



Earlier check for nullptr.
Merge internal change: 106859834



Quic streams honor RST_STREAM + NO_ERROR on the write side.

Override QuicDataStream CloseWriteSide method to honor QUIC_STREAM_NO_ERROR on
QUIC_VERSION_29 or later versions: send rst stream when writing to a stream
initiated by the peer is finished but incoming data hasn't been received
completely.
Merge internal change: 106853342



Add OnConnectionMigration method to QuicSentPacketManager. Add
OnConnectionMigration interface to SendAlgorithmInterface and RttStats. No
functional change expected.

This change is preparing to reset cwnd and rtt measurement when the client
migrates to a different network.
Merge internal change: 106851267




Factoring a QuicCryptoServerStreamBase API out of QuicCryptoServerStream
Merge internal change: 106845785



Deprecate --gfe2_reloadable_flag_quic_stop_checking_for_mismatch_ids
Merge internal change: 106845547



No functional change.  Minor change to reorder when the list of QuicAckListeners
is swapped into the TransmissionInfo in order to avoid an extra allocation.
Merge internal change: 106814823
==========

to

==========
Landing Recent QUIC changes until 2015-11-09 20:32 UTC



Add client-side support of cert transparency for QUIC, gated at QUIC_VERSION_30.

With this change, when the negotiated version > QUIC_VERSION_29, the client
indicates that it supports cert transparency in client hello, and caches the
CSCT value if it exists in server's response. However, the client NEITHER
demands SCT NOR verifies the received SCT (e.g., it is up to Chrome how to
verify).
Merge internal change: 107397642




Not sending QUIC packets if the send alarm is set. Behind
FLAGS_respect_send_alarm

This fixes a subtle bug where we weren't always respecting priorities when
writing.

I posit that if we are send limited by the sent packet manager, we expect to
resume with OnCanWrite, and resume the highest priority session.  Unfortunately
right now that's not the case.  When the highest priority session gets blocked
by the sent packet manager it schedules the alarm. However it's perfectly
possible that before the alarm fires, we get an incoming request, process it,
that stream checks to see if it can write, and when CanWrite checks now(), we
are past the time when the alarm should have fired (due to doing a lot of work,
busy machine, what have you) and write data for the random stream.
Merge internal change: 107380116



Add token binding negotiation to QUIC

This adds a tag (TBKP) to the SCFG and CHLO messages containing a taglist as a
value of the supported token binding key parameters (P256 is currently the only
supported param). This replaces the TLS token binding negotiation extension as
part of the broader Token Binding spec when done over QUIC.

Token binding negotiation is off by default - it must be turned on server-side
in QuicCryptoServerConfig::ConfigOptions and client side in
QuicCryptoClientConfig. If it is enabled, the application layer using QUIC must
handle the rest of the Token Binding protocol.

More information (including links to the Token Binding specs) is in this doc:
https://docs.google.com/document/d/12eKfkdC7g5IGUCtghzg7Wi__qiEkY65fX09n8sjLt...
Merge internal change: 107277639



Make comments for EndToEndTest.LargePostEarlyResponse more clear. Rearrange code
to clarifying the logic when sending request header and body separately.
Merge internal change: 107261172



Further reduce the number of QUIC end-to-end test variations that we run from 54
to 30, by only running the version negotiation variants when either all or none
of other options are enabled.

Among other things, this will help the perfomance of these test
in the Chrome memory bots.
Merge internal change: 107172676



Add some helper methods to QuicTestServer
Merge internal change: 107150707



Move the call to revive packets from QuicConnection::ProcessUdpPacket to
QuicConnection::OnPacketComplete. This avoid hitting a DCHECK in the EndToEnd
tests when: FEC is enabled, stateless rejects are enabled and packets are
reordered.
Merge internal change: 107136813



Reduce the number of QUIC end-to-end test combinations that are from from 240 to
46, by looking at five of the options, and only running when either none of
them, all of them or just one of them is enabled.
Merge internal change: 107135565



Add static MovePackets method to QUIC crypto_test_utils
Merge internal change: 107067016



Clean up "magic" constants in QuicFramerTest to add comments which explains
their values and extract out to named constants.
Merge internal change: 107036345




Replace QuicEncryptedPacket argument in QuicConnectionDebugVisitor::OnPacketSent
with an encrypted length. No functional change.
Merge internal change: 107034442




Override ReliableQuicStream::StopReading() to send RST_STREAM+NO_ERROR if
CloseWriteSide() is called before StopReading().

Currently we always call StopReading() before calling CloseWriteSide(). However,
there is not restriction to prevent calling StopReading() after CloseWrite(), in
which case we should also send a QUIC_STREAM_NO_ERROR rst to stop the peer to
sending more data. This feature improves RST_STREAM+NO_ERROR mechanism to be
more future-proof.
Merge internal change: 106990301




Update the comment of --quic_version.
Merge internal change: 106978852




Pass in connection ID and supported version to 
QuicFramer::BuildVersionNegotiationPacket, instead of passing in a
QuicPacketHeader and supported versions.
Merge internal change: 106955386




Change bufferring data structure for QuicStreamSequencer. Protected by
FLAGS_quic_use_stream_sequencer_buffer.
Swith QuicStreamSequencer's underlying data structure from QuicFrameList to
StreamSequencerBuffer.
Merge internal change: 106947577




Add include to reflect what is already used.
Merge internal change: 106946658



Add a data structure QuicMultipathTransmissionsMap which is not in use now.
QuicMultipathTransmissionsMap manages packets which are transmitted across
multiple paths. Also add a new struct QuicPathIdPacketNumber which comprises
both QuicPathId and QuicPacketNumber.
Merge internal change: 106938391



Earlier check for nullptr.
Merge internal change: 106859834



Quic streams honor RST_STREAM + NO_ERROR on the write side.

Override QuicDataStream CloseWriteSide method to honor QUIC_STREAM_NO_ERROR on
QUIC_VERSION_29 or later versions: send rst stream when writing to a stream
initiated by the peer is finished but incoming data hasn't been received
completely.
Merge internal change: 106853342



Add OnConnectionMigration method to QuicSentPacketManager. Add
OnConnectionMigration interface to SendAlgorithmInterface and RttStats. No
functional change expected.

This change is preparing to reset cwnd and rtt measurement when the client
migrates to a different network.
Merge internal change: 106851267




Factoring a QuicCryptoServerStreamBase API out of QuicCryptoServerStream
Merge internal change: 106845785



Deprecate --gfe2_reloadable_flag_quic_stop_checking_for_mismatch_ids
Merge internal change: 106845547



No functional change.  Minor change to reorder when the list of QuicAckListeners
is swapped into the TransmissionInfo in order to avoid an extra allocation.
Merge internal change: 106814823
==========

[rjshade, 2015-11-11 20:47:40]

Description was changed from

==========
Landing Recent QUIC changes until 2015-11-09 20:32 UTC



Add client-side support of cert transparency for QUIC, gated at QUIC_VERSION_30.

With this change, when the negotiated version > QUIC_VERSION_29, the client
indicates that it supports cert transparency in client hello, and caches the
CSCT value if it exists in server's response. However, the client NEITHER
demands SCT NOR verifies the received SCT (e.g., it is up to Chrome how to
verify).
Merge internal change: 107397642




Not sending QUIC packets if the send alarm is set. Behind
FLAGS_respect_send_alarm

This fixes a subtle bug where we weren't always respecting priorities when
writing.

I posit that if we are send limited by the sent packet manager, we expect to
resume with OnCanWrite, and resume the highest priority session.  Unfortunately
right now that's not the case.  When the highest priority session gets blocked
by the sent packet manager it schedules the alarm. However it's perfectly
possible that before the alarm fires, we get an incoming request, process it,
that stream checks to see if it can write, and when CanWrite checks now(), we
are past the time when the alarm should have fired (due to doing a lot of work,
busy machine, what have you) and write data for the random stream.
Merge internal change: 107380116



Add token binding negotiation to QUIC

This adds a tag (TBKP) to the SCFG and CHLO messages containing a taglist as a
value of the supported token binding key parameters (P256 is currently the only
supported param). This replaces the TLS token binding negotiation extension as
part of the broader Token Binding spec when done over QUIC.

Token binding negotiation is off by default - it must be turned on server-side
in QuicCryptoServerConfig::ConfigOptions and client side in
QuicCryptoClientConfig. If it is enabled, the application layer using QUIC must
handle the rest of the Token Binding protocol.

More information (including links to the Token Binding specs) is in this doc:
https://docs.google.com/document/d/12eKfkdC7g5IGUCtghzg7Wi__qiEkY65fX09n8sjLt...
Merge internal change: 107277639



Make comments for EndToEndTest.LargePostEarlyResponse more clear. Rearrange code
to clarifying the logic when sending request header and body separately.
Merge internal change: 107261172



Further reduce the number of QUIC end-to-end test variations that we run from 54
to 30, by only running the version negotiation variants when either all or none
of other options are enabled.

Among other things, this will help the perfomance of these test
in the Chrome memory bots.
Merge internal change: 107172676



Add some helper methods to QuicTestServer
Merge internal change: 107150707



Move the call to revive packets from QuicConnection::ProcessUdpPacket to
QuicConnection::OnPacketComplete. This avoid hitting a DCHECK in the EndToEnd
tests when: FEC is enabled, stateless rejects are enabled and packets are
reordered.
Merge internal change: 107136813



Reduce the number of QUIC end-to-end test combinations that are from from 240 to
46, by looking at five of the options, and only running when either none of
them, all of them or just one of them is enabled.
Merge internal change: 107135565



Add static MovePackets method to QUIC crypto_test_utils
Merge internal change: 107067016



Clean up "magic" constants in QuicFramerTest to add comments which explains
their values and extract out to named constants.
Merge internal change: 107036345




Replace QuicEncryptedPacket argument in QuicConnectionDebugVisitor::OnPacketSent
with an encrypted length. No functional change.
Merge internal change: 107034442




Override ReliableQuicStream::StopReading() to send RST_STREAM+NO_ERROR if
CloseWriteSide() is called before StopReading().

Currently we always call StopReading() before calling CloseWriteSide(). However,
there is not restriction to prevent calling StopReading() after CloseWrite(), in
which case we should also send a QUIC_STREAM_NO_ERROR rst to stop the peer to
sending more data. This feature improves RST_STREAM+NO_ERROR mechanism to be
more future-proof.
Merge internal change: 106990301




Update the comment of --quic_version.
Merge internal change: 106978852




Pass in connection ID and supported version to 
QuicFramer::BuildVersionNegotiationPacket, instead of passing in a
QuicPacketHeader and supported versions.
Merge internal change: 106955386




Change bufferring data structure for QuicStreamSequencer. Protected by
FLAGS_quic_use_stream_sequencer_buffer.
Swith QuicStreamSequencer's underlying data structure from QuicFrameList to
StreamSequencerBuffer.
Merge internal change: 106947577




Add include to reflect what is already used.
Merge internal change: 106946658



Add a data structure QuicMultipathTransmissionsMap which is not in use now.
QuicMultipathTransmissionsMap manages packets which are transmitted across
multiple paths. Also add a new struct QuicPathIdPacketNumber which comprises
both QuicPathId and QuicPacketNumber.
Merge internal change: 106938391



Earlier check for nullptr.
Merge internal change: 106859834



Quic streams honor RST_STREAM + NO_ERROR on the write side.

Override QuicDataStream CloseWriteSide method to honor QUIC_STREAM_NO_ERROR on
QUIC_VERSION_29 or later versions: send rst stream when writing to a stream
initiated by the peer is finished but incoming data hasn't been received
completely.
Merge internal change: 106853342



Add OnConnectionMigration method to QuicSentPacketManager. Add
OnConnectionMigration interface to SendAlgorithmInterface and RttStats. No
functional change expected.

This change is preparing to reset cwnd and rtt measurement when the client
migrates to a different network.
Merge internal change: 106851267




Factoring a QuicCryptoServerStreamBase API out of QuicCryptoServerStream
Merge internal change: 106845785



Deprecate --gfe2_reloadable_flag_quic_stop_checking_for_mismatch_ids
Merge internal change: 106845547



No functional change.  Minor change to reorder when the list of QuicAckListeners
is swapped into the TransmissionInfo in order to avoid an extra allocation.
Merge internal change: 106814823
==========

to

==========
Landing Recent QUIC changes until 2015-11-09 20:32 UTC


Add client-side support of cert transparency for QUIC, gated at QUIC_VERSION_30.

With this change, when the negotiated version > QUIC_VERSION_29, the client
indicates that it supports cert transparency in client hello, and caches the
CSCT value if it exists in server's response. However, the client NEITHER
demands SCT NOR verifies the received SCT (e.g., it is up to Chrome how to
verify).
Merge internal change: 107397642
https://codereview.chromium.org/1435943002/


Not sending QUIC packets if the send alarm is set. Behind
FLAGS_respect_send_alarm

This fixes a subtle bug where we weren't always respecting priorities when
writing.

I posit that if we are send limited by the sent packet manager, we expect to
resume with OnCanWrite, and resume the highest priority session.  Unfortunately
right now that's not the case.  When the highest priority session gets blocked
by the sent packet manager it schedules the alarm. However it's perfectly
possible that before the alarm fires, we get an incoming request, process it,
that stream checks to see if it can write, and when CanWrite checks now(), we
are past the time when the alarm should have fired (due to doing a lot of work,
busy machine, what have you) and write data for the random stream.
Merge internal change: 107380116
https://codereview.chromium.org/1439653002/


Add token binding negotiation to QUIC

This adds a tag (TBKP) to the SCFG and CHLO messages containing a taglist as a
value of the supported token binding key parameters (P256 is currently the only
supported param). This replaces the TLS token binding negotiation extension as
part of the broader Token Binding spec when done over QUIC.

Token binding negotiation is off by default - it must be turned on server-side
in QuicCryptoServerConfig::ConfigOptions and client side in
QuicCryptoClientConfig. If it is enabled, the application layer using QUIC must
handle the rest of the Token Binding protocol.

More information (including links to the Token Binding specs) is in this doc:
https://docs.google.com/document/d/12eKfkdC7g5IGUCtghzg7Wi__qiEkY65fX09n8sjLt...
Merge internal change: 107277639
https://codereview.chromium.org/1437893002/


Make comments for EndToEndTest.LargePostEarlyResponse more clear. Rearrange code
to clarifying the logic when sending request header and body separately.
Merge internal change: 107261172
https://codereview.chromium.org/1433353002/


Further reduce the number of QUIC end-to-end test variations that we run from 54
to 30, by only running the version negotiation variants when either all or none
of other options are enabled.

Among other things, this will help the perfomance of these test
in the Chrome memory bots.
Merge internal change: 107172676
https://codereview.chromium.org/1414953012/


Add some helper methods to QuicTestServer
Merge internal change: 107150707
https://codereview.chromium.org/1433813002/


Move the call to revive packets from QuicConnection::ProcessUdpPacket to
QuicConnection::OnPacketComplete. This avoid hitting a DCHECK in the EndToEnd
tests when: FEC is enabled, stateless rejects are enabled and packets are
reordered.
Merge internal change: 107136813
https://codereview.chromium.org/1419303009/


Reduce the number of QUIC end-to-end test combinations that are from from 240 to
46, by looking at five of the options, and only running when either none of
them, all of them or just one of them is enabled.
Merge internal change: 107135565
https://codereview.chromium.org/1418503022/


Clean up "magic" constants in QuicFramerTest to add comments which explains
their values and extract out to named constants.
Merge internal change: 107036345
https://codereview.chromium.org/1435673002/


Replace QuicEncryptedPacket argument in QuicConnectionDebugVisitor::OnPacketSent
with an encrypted length. No functional change.
Merge internal change: 107034442
https://codereview.chromium.org/1433783004/


Override ReliableQuicStream::StopReading() to send RST_STREAM+NO_ERROR if
CloseWriteSide() is called before StopReading().

Currently we always call StopReading() before calling CloseWriteSide(). However,
there is not restriction to prevent calling StopReading() after CloseWrite(), in
which case we should also send a QUIC_STREAM_NO_ERROR rst to stop the peer to
sending more data. This feature improves RST_STREAM+NO_ERROR mechanism to be
more future-proof.
Merge internal change: 106990301
https://codereview.chromium.org/1433063002/


Update the comment of --quic_version.
Merge internal change: 106978852
https://codereview.chromium.org/1425823005/


Pass in connection ID and supported version to 
QuicFramer::BuildVersionNegotiationPacket, instead of passing in a
QuicPacketHeader and supported versions.
Merge internal change: 106955386
https://codereview.chromium.org/1433703005/


Change bufferring data structure for QuicStreamSequencer. Protected by
FLAGS_quic_use_stream_sequencer_buffer.
Swith QuicStreamSequencer's underlying data structure from QuicFrameList to
StreamSequencerBuffer.
Merge internal change: 106947577
https://codereview.chromium.org/1433793002/


Add include to reflect what is already used.
Merge internal change: 106946658
https://codereview.chromium.org/1433013003/


Add a data structure QuicMultipathTransmissionsMap which is not in use now.
QuicMultipathTransmissionsMap manages packets which are transmitted across
multiple paths. Also add a new struct QuicPathIdPacketNumber which comprises
both QuicPathId and QuicPacketNumber.
Merge internal change: 106938391
https://codereview.chromium.org/1431363002/


Earlier check for nullptr.
Merge internal change: 106859834
https://codereview.chromium.org/1433783003/


Quic streams honor RST_STREAM + NO_ERROR on the write side.

Override QuicDataStream CloseWriteSide method to honor QUIC_STREAM_NO_ERROR on
QUIC_VERSION_29 or later versions: send rst stream when writing to a stream
initiated by the peer is finished but incoming data hasn't been received
completely.
Merge internal change: 106853342
https://codereview.chromium.org/1413373013/


Add OnConnectionMigration method to QuicSentPacketManager. Add
OnConnectionMigration interface to SendAlgorithmInterface and RttStats. No
functional change expected.

This change is preparing to reset cwnd and rtt measurement when the client
migrates to a different network.
Merge internal change: 106851267
https://codereview.chromium.org/1435553004/


Factoring a QuicCryptoServerStreamBase API out of QuicCryptoServerStream
Merge internal change: 106845785
https://codereview.chromium.org/1413613016/


Deprecate --gfe2_reloadable_flag_quic_stop_checking_for_mismatch_ids
Merge internal change: 106845547
https://codereview.chromium.org/1418963008/


No functional change.  Minor change to reorder when the list of QuicAckListeners
is swapped into the TransmissionInfo in order to avoid an extra allocation.
Merge internal change: 106814823
https://codereview.chromium.org/1428303003/
==========

[rjshade, 2015-11-11 20:56:01]

rjshade@chromium.org changed reviewers:
+ rch@chromium.org

[Ryan Hamilton, 2015-11-11 22:14:54]

Oh, here it is! LGTM

[rjshade, 2015-11-12 17:30:44]

The CQ bit was checked by rjshade@chromium.org

[commit-bot: I haz the power, 2015-11-12 17:31:06]

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

[commit-bot: I haz the power, 2015-11-12 17:40:44]

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

[commit-bot: I haz the power, 2015-11-12 17:40:45]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[rjshade, 2015-11-12 17:45:31]

The CQ bit was checked by rjshade@chromium.org

[rjshade, 2015-11-12 17:45:32]

The patchset sent to the CQ was uploaded after l-g-t-m from rch@chromium.org
Link to the patchset: https://codereview.chromium.org/1437023002/#ps40001
(title: " ")

[commit-bot: I haz the power, 2015-11-12 17:46:18]

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

[commit-bot: I haz the power, 2015-11-12 18:01:28]

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

[commit-bot: I haz the power, 2015-11-12 18:01:29]

Try jobs failed on following builders:
  linux_chromium_compile_dbg_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[rjshade, 2015-11-12 18:53:58]

The CQ bit was checked by rjshade@chromium.org

[rjshade, 2015-11-12 18:53:59]

The patchset sent to the CQ was uploaded after l-g-t-m from rch@chromium.org
Link to the patchset: https://codereview.chromium.org/1437023002/#ps60001
(title: " ")

[commit-bot: I haz the power, 2015-11-12 18:55:50]

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

[commit-bot: I haz the power, 2015-11-12 20:16:33]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2015-11-12 20:17:41]

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