[quicwg/base-drafts] 594ab5: Define requirements for handling packets

Martin Thomson <martin.thomson@gmail.com> Fri, 11 August 2017 06:50 UTC

DomainKey-Signature: a=rsa-sha1; c=nofws; d=github.com; s=mailo; q=dns; h=Sender: Date: From: Reply-To: To: Message-ID: Subject: Mime-Version: Content-Type: Content-Transfer-Encoding; b=o5X8SDwDpPm1rwgx8LPRd+254KlteOcm30pjsVaYeAjPzdiBx1aOlQaJxWdupqXf7t5l9R 0AQnnko6//X3vK3olWXTTqKh1WJrUXMi8GDjGYBBzqkaw7eL5Z+TKqK1lQPnLZxyiBaeyFoS 0d1qP5lIoaO54xYU0WSjMWEhQo9Ns=
Sender: martin.thomson=gmail.com@github.com
Date: Thu, 10 Aug 2017 23:50:37 -0700
From: Martin Thomson <martin.thomson@gmail.com>
Reply-To: Martin Thomson <martin.thomson@gmail.com>
To: quic-issues@ietf.org
Message-ID: <598d53bddf958_43e3f99dfad9c34628fe@hookshot-fe2-cp1-prd.iad.github.net.mail>
Subject: [quicwg/base-drafts] 594ab5: Define requirements for handling packets
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="--==_mimepart_598d53bddf5ab_43e3f99dfad9c34627da"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/uXx4MCgucgCFYr59Wrg4pLDjkhM>
Precedence: list

  Branch: refs/heads/packet-handling
  Home:   https://github.com/quicwg/base-drafts
  Commit: 594ab51b68a4b451a613ab89d1cca55cb29d63e7
      https://github.com/quicwg/base-drafts/commit/594ab51b68a4b451a613ab89d1cca55cb29d63e7
  Author: Martin Thomson <martin.thomson@gmail.com>
  Date:   2017-08-11 (Fri, 11 Aug 2017)

  Changed paths:
    M draft-ietf-quic-transport.md

  Log Message:
  -----------
  Define requirements for handling packets

We never really said how to handle incoming packets.  This adds a section on
that.  This was originally motivated by #570, where the rules for what to
generate a Version Negotiation packet for were a little unclear.

Now though, this is a far more comprehensive description of what to do with
a packet that is received.

For #570, I've chosen to limit packet size.  If the packet is too small, then
this requires the server to drop the packet.  In response to the potential for
a future version of QUIC to define a smaller initial packet (@mikkelfj raised
this point), I've included advice on what might be done to avoid having packets
discarded.

I realize that we don't have a patch that sets the packet size to 1200.  I'm
going to write that one now.  This depends on that.

[quicwg/base-drafts] 594ab5: Define requirements … Martin Thomson