Skip to content

Commit

Permalink
Replace algorithm with example
Browse files Browse the repository at this point in the history
  • Loading branch information
MikeBishop committed Mar 14, 2018
1 parent 808465e commit f6157a0
Showing 1 changed file with 13 additions and 16 deletions.
29 changes: 13 additions & 16 deletions draft-ietf-quic-transport.md
Expand Up @@ -1163,27 +1163,24 @@ An endpoint MAY use the following transport parameters:
initial_max_streams_bidi (0x0002):

: The initial maximum streams parameter contains the initial maximum number of
bidirectional streams the peer may initiate, encoded as an unsigned 16-bit
integer. The maximum bidirectional stream ID is set to 0 if this parameter is
absent or zero, preventing the creation of new bidirectional streams until a
application-owned bidirectional streams the peer may initiate, encoded as an
unsigned 16-bit integer. If this parameter is absent or zero,
application-owned bidirectional streams cannot be created until a
MAX_STREAM_ID frame is sent. Note that a value of 0 does not prevent the
cryptographic handshake stream (that is, stream 0) from being used. Non-zero
values are converted to a valid bidirectional stream ID for a peer-initiated
stream (that is, after shifting two bits to the left, clients subtract 0 and
servers subtract 3). Setting this parameter is equivalent to sending a
MAX_STREAM_ID ({{frame-max-stream-id}}) immediately after completing the
handshake containing the resulting Stream ID.
cryptographic handshake stream (that is, stream 0) from being used. For
example, a value of 0x05 would be translated to a bidirectional stream ID of
20 by a client or 17 by a server. Setting this parameter is equivalent to
sending a MAX_STREAM_ID ({{frame-max-stream-id}}) immediately after completing
the handshake containing the resulting Stream ID.

initial_max_stream_id_uni (0x0008):

: The initial maximum streams parameter contains the initial maximum number of
unidirectional streams the peer may initiate, encoded as an unsigned 16-bit
integer. The maximum unidirectional stream ID is set to 0 if this parameter
is absent or zero, preventing the creation of new unidirectional streams until
a MAX_STREAM_ID frame is sent. Non-zero values are converted to a valid
bidirectional stream ID for a peer-initiated stream (that is, after shifting
two bits to the left, clients subtract 2 and servers subtract 1). Setting
this parameter is equivalent to sending a MAX_STREAM_ID
application-owned unidirectional streams the peer may initiate, encoded as an
unsigned 16-bit integer. If this parameter is absent or zero, unidirectional
streams cannot be created until a MAX_STREAM_ID frame is sent. For example, a
value of 0x05 would be translated to a value of 18 by a client or 19 by a
server. Setting this parameter is equivalent to sending a MAX_STREAM_ID
({{frame-max-stream-id}}) immediately after completing the handshake
containing the resulting Stream ID.

Expand Down

0 comments on commit f6157a0

Please sign in to comment.