Re: stateless reset in response to packet that is 43 bytes

Ian Swett <ianswett@google.com> Mon, 01 June 2020 04:54 UTC

MIME-Version: 1.0
References: <CAG9+TpZujQdj2OwJjnVOGQS942--wTuRN7n+MsHTjxYUhNtLdQ@mail.gmail.com> <755286bf-348d-4272-8905-ab71c8dd0cc0@www.fastmail.com>
In-Reply-To: <755286bf-348d-4272-8905-ab71c8dd0cc0@www.fastmail.com>
From: Ian Swett <ianswett@google.com>
Date: Mon, 01 Jun 2020 00:54:11 -0400
Message-ID: <CAKcm_gNF3rLJ8_eAOTwukhW+uYM1oTSzjA3a3Xm2bW7fYiNjNg@mail.gmail.com>
Subject: Re: stateless reset in response to packet that is 43 bytes
To: Martin Thomson <mt@lowentropy.net>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ac33a805a6fe96a7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/x3C_uia6QkRGpTo3_GBNUqLXAiw>
Precedence: list

I believe we assumed 1 byte of payload as well, so I believe 43 is correct.

On Sun, May 31, 2020 at 9:34 PM Martin Thomson <mt@lowentropy.net> wrote:

> The packet with a short header that has the lowest length, but a
> maximum-length connection ID is 1 (type) + 20 (destination connection ID) +
> 4 (packet number + data) + 16 (aead expansion) = 41 bytes.
>
> Hmm, maybe this should be 42 instead of 43.  I always get this bit wrong
> though.
>
> On Mon, Jun 1, 2020, at 02:55, Jiuhai Zhang wrote:
> > https://tools.ietf.org/html/draft-ietf-quic-transport-27#section-10.4
> > An endpoint that sends a stateless reset in response to
> >    packet that is 43 bytes or less in length SHOULD send a stateless
> >    reset that is one byte shorter than the packet it responds to.
> > Could someone explain why it is 43 bytes? thks
>
>

stateless reset in response to packet that is 43 … Jiuhai Zhang
Re: stateless reset in response to packet that is… Martin Thomson
Re: stateless reset in response to packet that is… Ian Swett
Re: stateless reset in response to packet that is… Martin Thomson