Skip to content

send two ClientHello packets, potentially with different sizes #3775

@marten-seemann

Description

@marten-seemann

This serves three purposes:

  1. It protects against loss of the ClientHello.
  2. It opens up the amplification window.
  3. It can be used for detecting the Path MTU very early during the connection.

Number 3 is most useful if the server latches onto that larger MTU. It probably makes the most sense to make the first packet larger than the second one, since that increases the likelihood that the first ACK will be for that packet.

We need to check what happens if one of these is packets is lost. Obviously, this should not trigger a retransmission. I think that our retransmission logic ensures that, but I'm not 100% sure.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions