From b6d3a89e9ff096befb74196f6b7bcfda4fe7fc15 Mon Sep 17 00:00:00 2001 From: Dmitri Tikhonov Date: Thu, 14 May 2020 09:00:22 -0400 Subject: [PATCH] Fix two typos in the transport draft --- draft-ietf-quic-transport.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index 85ea8ee3d1..339cf32985 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -256,7 +256,7 @@ x (i): x (A..B): : Indicates that x can be any length from A to B; A can be omitted to indicate - a mimumum of zero bits and B can be omitted to indicate no set upper limit; + a minimum of zero bits and B can be omitted to indicate no set upper limit; values in this format always end on an octet boundary x (?) = C: @@ -3811,7 +3811,7 @@ One way to construct a probe for the path MTU is to coalesce (see header packet in a single UDP datagram. If the UDP datagram reaches the endpoint, the Handshake packet will be ignored, but the short header packet will be acknowledged. If the UDP datagram causes an ICMP message to be sent, the -first part of the datagram will be quoted in that message. If the the source +first part of the datagram will be quoted in that message. If the source connection ID is within the quoted portion of the UDP datagram, that could be used for routing.