summaryrefslogtreecommitdiffstats
path: root/net/quic/quic_packet_creator.h
diff options
context:
space:
mode:
authorrtenneti@chromium.org <rtenneti@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-05-09 12:29:33 +0000
committerrtenneti@chromium.org <rtenneti@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-05-09 12:29:33 +0000
commit2532de12bd5d83ef4de1a50837709086c3a25ca0 (patch)
treea9a8cb66410b96632e1d270ed3420e35131c4ff0 /net/quic/quic_packet_creator.h
parentda29a20567c029ec25cd7ab7a167532ffd7c0010 (diff)
downloadchromium_src-2532de12bd5d83ef4de1a50837709086c3a25ca0.zip
chromium_src-2532de12bd5d83ef4de1a50837709086c3a25ca0.tar.gz
chromium_src-2532de12bd5d83ef4de1a50837709086c3a25ca0.tar.bz2
Land Recent QUIC changes
QUIC: use QuicTag/QuicTagVector throughout. crypto_protocol.h has had CryptoTag and CryptoTagVector. Then quic_protocol.h got QuicVersionTag and QuicVersionTagList because it didn't want to depend on crypto_protocol.h This change uses a single QuicTag and QuicTagVector throughout the code, including the crypto code. Merge internal change: 45230337 QUIC: move random values to the beginning and the certifiate chain to the end. jar suggested that the certificate chain should have a tag that will cause it to be sorted at the end of any handshake messages because it's likely to be large and the client might be able to get everything that it needs from the small values at the beginning. Likewise he argued that tags with random values should be towards the beginning of the message because the server mightn't hold state for a rejected client hello and therefore the client may have issues reassembling the rejection message in the event that it sent two client hellos. This change tweaks the tag values to achieve that ordering. Merge internal change: 45228375 Removing obselete TODOs Merge internal change: 45219448 Use the idle connection state timeout negotiated in crypto handshake. Merge internal change: 45176251 QUIC: address wtc's followup comments on cl/44792710. This change addresses wtc's comments on cl/44792710. There should be no semantic differences. Merge internal change: 45051718 QUIC - Fixed HasRetransmittableData enum to have the correct values. Fixed comments from rch Merge internal change: 45143336 Change the QUIC version number to a new value which is amenable to frequent i ncrementing. Merge internal change: 45111687 QUIC: run clang-format over .../quic/crypto. I ran: for x in $(ls -1 *.cc *.h) ; do clang-format -i $x -style Google; echo $x; done And then used git add -p to manually review the changes. In the cases where I didn't care, I went with what the tool produced. Merge internal change: 45053104 QUIC: address wtc's followup comments on cl/44792710. This change addresses wtc's comments on cl/44792710. There should be no semantic differences. Merge internal change: 45051718 Minor cleanup of ReliableQuicStreamTest output. Also change MockConnection to create a NiceMock version of the Helper to avoid annoying GMock messages. Merge internal change: 45010564 QUIC: partly deflake EndToEndTest.LargePost Since cl/44690884, some runs of this test have timed out. Everything appears to be working ok, just not fast enough. It's possible that the additional packet `losses' caused by decryption failures when we lose the client hello are convincing the congestion control that the loss rate is very high. However, since I have a trip to NIST this week, this change removes the flake by reverting a tiny part of cl/44690884. Sadly there is another flake in the test which this CL doesn't fix. Details in the bug. Merge internal change: 45008247 Fix a bug in QUIC header compression handling where buffered headers were not handled properly. Merge internal change: 45007035 QUIC: tiny test cleanup. wtc suggested this in a post-submission comment. Merge internal change: 44898354 QUIC: add expiry to server configs and have the GFE generate random server configs. Server configs need an expiry because they are effectively certificates. This change has the GFE generate server configs with the same expiry as the primary certificate. It also switches the GFE to generating random server configs at startup. (Random in the sense of random keys and orbit values.) Originally I wanted to have the server config persist over a restart and so derived them, deterministically, from the primary, private key with a todo to diversify the orbit. However, since we don't have any shared strike registers at the moment that doesn't seem to be worth the complexity. Also, figuring out how to diversify the orbit value in a per-GFE sense is really messy (include the hostname? include the port? Which port?). So this CL goes for simple and secure. Merge internal change: 44898035 QUIC: use 24-bit lengths for public values. If ideal lattices don't work out then we may end up with Diffie-Hellman public values that are larger than 16-bits. (Hopefully not, but you never know.) Merge internal change: 44897191 QUIC: have the client echo the server's nonce. This reflects a comment from wtc previously that this would be a good idea. Merge internal change: 44896699 QUIC: steps 12 and 13, forward secure mode. Merge internal change: 44896363 Fix LOG(DFATAL) when client sends invalid stream frame with fin. Merge internal change: 44871764 R=rch@chromium.org Review URL: https://chromiumcodereview.appspot.com/14816006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199190 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/quic/quic_packet_creator.h')
-rw-r--r--net/quic/quic_packet_creator.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/net/quic/quic_packet_creator.h b/net/quic/quic_packet_creator.h
index 2e5c596..6f557c0a 100644
--- a/net/quic/quic_packet_creator.h
+++ b/net/quic/quic_packet_creator.h
@@ -120,7 +120,7 @@ class NET_EXPORT_PRIVATE QuicPacketCreator : public QuicFecBuilderInterface {
// serialized packet to a random bool and returns that value as a member of
// SerializedPacket.
QuicEncryptedPacket* SerializeVersionNegotiationPacket(
- const QuicVersionTagList& supported_versions);
+ const QuicTagVector& supported_versions);
QuicPacketSequenceNumber sequence_number() const {
return sequence_number_;