From 212a0da8555f1553721e5197c34200d98470c572 Mon Sep 17 00:00:00 2001 From: Julian Reschke Date: Thu, 25 Jan 2018 08:06:14 +0100 Subject: [PATCH] consistent artwork typing --- draft-ietf-quic-http.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index a94b8ae5eb..960ac17249 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -407,13 +407,13 @@ push stream always begins with a header (see {{fig-push-stream-header}}) that identifies the Push ID of the promise that it fulfills, encoded as a variable-length integer. -~~~~~ +~~~~~~~~~~ drawing 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Push ID (i) ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -~~~~~ +~~~~~~~~~~ {: #fig-push-stream-header title="Push Stream Header"} A server SHOULD use Push IDs sequentially, starting at 0. A client uses the