Frame Type was inconsistently labelled (#1527)

quicwg · Jul 6, 2018 · 8d1fb47 · 8d1fb47
1 parent 7459593
commit 8d1fb47
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md
@@ -1007,7 +1007,7 @@ additional type-dependent fields:
  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
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
-|                           Type (i)                          ...
+|                       Frame Type (i)                        ...
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                   Type-Dependent Fields (*)                 ...
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
@@ -1058,6 +1058,7 @@ are always encoded as a single octet with the value 0x07.  An endpoint MUST
 treat the receipt of a frame type that uses a longer encoding than necessary as
 a connection error of type PROTOCOL_VIOLATION.
 
+
 ## Extension Frames
 
 QUIC frames do not use a self-describing encoding.  An endpoint therefore needs