commit d3a1de96ef178e128273c278eb2f610bae859c04
author fkastenholz <fkastenholz@google.com> Wed May 15 07:00:07 2019 -0700
committer Copybara-Service <copybara-worker@google.com> Wed May 15 18:00:48 2019 -0700
tree a1c04b2f33d3a241368daf0ebb5428b829bd13ac
parent 9838104e6baf971bdb329ba71a76ea7754b79e1d

Have separate uni- and bi-directional stream limits for IETF QUIC

IETF QUIC supports unidirectional and bidirectional streams, each
of which can have a different stream limit. The stream limit is first
negotiated using the transport parameters.  This change connects the
transport parameters to the stream-id-manager so that the former
can configure both the types of streams.

gfe-relnote: N/A all for version99 code.
PiperOrigin-RevId: 248325885
Change-Id: I4675c147dfda856b73337aac87a4290958599a18

quic/core/crypto/crypto_handshake_message.cc

diff --git a/quic/core/crypto/crypto_handshake_message.cc b/quic/core/crypto/crypto_handshake_message.cc
index 1bbed74..579bb37 100644
--- a/quic/core/crypto/crypto_handshake_message.cc
+++ b/quic/core/crypto/crypto_handshake_message.cc
@@ -274,7 +274,8 @@
       case kCFCW:
       case kSFCW:
       case kIRTT:
-      case kMIDS:
+      case kMIUS:
+      case kMIBS:
       case kSCLS:
       case kTCID:
         // uint32_t value