Add max_bandwidth and max_bandwidth_timestamp to QUIC source address

net/quic/crypto/source_address_token.h

Index: net/quic/crypto/source_address_token.h
diff --git a/net/quic/crypto/source_address_token.h b/net/quic/crypto/source_address_token.h
index c719fef0412a3c4570a76f7ba163cf4153df2b45..7d4edb813fc0eb68f59d7970bf8c53abd8391be5 100644
--- a/net/quic/crypto/source_address_token.h
+++ b/net/quic/crypto/source_address_token.h
@@ -42,6 +42,23 @@ class CachedNetworkParameters {
     bandwidth_estimate_bytes_per_second_ = bandwidth_estimate_bytes_per_second;
   }
 
+  int32 max_bandwidth_estimate_bytes_per_second() const {
+    return max_bandwidth_estimate_bytes_per_second_;
+  }
+  void set_max_bandwidth_estimate_bytes_per_second(
+      int32 max_bandwidth_estimate_bytes_per_second) {
+    max_bandwidth_estimate_bytes_per_second_ =
+        max_bandwidth_estimate_bytes_per_second;
+  }
+
+  int32 max_bandwidth_timestamp_seconds() const {
+    return max_bandwidth_timestamp_seconds_;
+  }
+  void set_max_bandwidth_timestamp_seconds(
+      int32 max_bandwidth_timestamp_seconds) {
+    max_bandwidth_timestamp_seconds_ = max_bandwidth_timestamp_seconds;
+  }
+
   int32 min_rtt_ms() const {
     return min_rtt_ms_;
   }
@@ -66,6 +83,11 @@ class CachedNetworkParameters {
   // The server can supply a bandwidth estimate (in bytes/s) which it may re-use
   // on receipt of a source-address token with this field set.
   int32 bandwidth_estimate_bytes_per_second_;
+  // The maximum bandwidth seen to the client, not necessarily the latest.

[wtc, 2014/08/14 01:49:10]

Nit: seen to the client => seen by the client ?

[ramant (doing other things), 2014/08/14 19:48:04]

Done.

+  int32 max_bandwidth_estimate_bytes_per_second_;
+  // Timestamp (seconds since UNIX epoch) that indicates when the max bandwidth
+  // was seen by the server.
+  int32 max_bandwidth_timestamp_seconds_;

[wtc, 2014/08/14 01:49:10]

IMPORTANT: this signed 32-bit integer will overflow in year 2038. This is the
Unix year 2038 problem. Can this be an int64?

[ramant (doing other things), 2014/08/14 19:48:04]

Filed b/17035772. Chromium is not yet using this code. Will fix in the internal
source also.

[ramant (doing other things), 2014/08/14 19:52:09]

Done.

   // The min RTT seen on a previous connection can be used by the server to
   // inform initial connection parameters for new connections.
   int32 min_rtt_ms_;