From 6bd8826c2a09264940e77db5fa20e27a496a4522 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Fri, 28 Apr 2017 11:57:48 +1000 Subject: [PATCH] Don't require the client to reset excess streams In 0-RTT, the client might overrun the server's stream limit. Let the server work out what to do about that. Closes #425 --- draft-ietf-quic-transport.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index a9542daf63..9bb1fda71e 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -1045,9 +1045,8 @@ particularly with respect to transport parameters that establish limits: limit is received, the client can recommence sending. * Similarly, a client might exceed the initial stream limit declared by the - server. A client MUST reset any streams that exceed this limit. A server - SHOULD reset any streams it cannot handle with a code that allows the client - to retry any application action bound to those streams. + server. A server MAY reset any streams it cannot handle with a code that + allows the client to retry any application action bound to those streams. A server MAY close a connection if remembered or assumed 0-RTT transport parameters cannot be supported, using an error code that is appropriate to the