Handshake timeout failures?

Martin Duke <martin.h.duke@gmail.com> Mon, 08 July 2019 21:34 UTC

Return-Path: <martin.h.duke@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8040120280 for <quic@ietfa.amsl.com>; Mon, 8 Jul 2019 14:34:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.703
X-Spam-Level:
X-Spam-Status: No, score=-0.703 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zOS-IVIhoGtl for <quic@ietfa.amsl.com>; Mon, 8 Jul 2019 14:34:14 -0700 (PDT)
Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B92AF1201D0 for <quic@ietf.org>; Mon, 8 Jul 2019 14:34:13 -0700 (PDT)
Received: by mail-wr1-x42e.google.com with SMTP id c2so18677243wrm.8 for <quic@ietf.org>; Mon, 08 Jul 2019 14:34:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=HCfe1g3eLrN7XQ3K5D7ojqS0eP0MdjoL14CCf98BzPk=; b=Vk7zivNZqNjivvT13hKEXtfD47oCRKdtrjXfgpjHs1aTLjcTgTWbLynP417BCfup9z kvOKXwgf36zkS+KBUVFMY6A7atynrJ2H7b0zVVLptDYwt56ubmQpTWFPIv7Nk2kw9OIs 0a4WbBMmB3PegunmIQbxl6u2p5JQ1jYY7oung9LnC2LHCQqQZ4T2azYv0X2det/Qt2DR aT+7J1wVuatNFyNmK7fPYPsAw+v84GGqy621uFOsCdiDJR+fV729txoCgRDvKiz8MCot Zqf/gdrtYqxGVoolDKm0n7H9ZbRMrNi8KCA5MLJalENSFiYLgWzranb+KtKDBYwtypFQ nMUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=HCfe1g3eLrN7XQ3K5D7ojqS0eP0MdjoL14CCf98BzPk=; b=rS9PJX6V1lLmm6/Igx2eqgrrflhlhQ/RdL00hCWDrghw90W8Q9ug02i061lbbXkRDS ofhmITgY59kTdXs+G3w9JtYRGEhse4F16L/X27WwYhFWRQceVyJJkj1ktbNTCAURAGWy 4Ox3hW7XR1zCbqxKc+T30+PL2oqkNTue6IXc7e48SuwK76BoFPOMWwYjMk5k0Ow1vMNT LnoDcf4fgkNcOrfk7wR7b80pBDasDzwSnYI0pjQcZMHJgvsRuD2zHRu9Gh0QgrO5ggxb vzJ6stg/zipzIfvMb9WSIt0AuL662sYe7CVtccXBqxOAuQ9VmEQ/DJm0kacTfN8NWjH+ wgew==
X-Gm-Message-State: APjAAAUYqzmUbAQj6eF+W3yYaW5o+RUwGvhvbFKgALdey0MFe1sNG1cV sOrekvnRNL4TN/pK1bK8YhjET9XKFMtNKr2E08sHXMmC
X-Google-Smtp-Source: APXvYqyljYIQ9oA3KrQnGwxkFwtA45MVl0T0r/rBo/0Y1JkCUs3CDNiagMWinCvAmySAMQHdg3IRvWIBZar6r5+3OHU=
X-Received: by 2002:adf:f646:: with SMTP id x6mr15905214wrp.18.1562621651969; Mon, 08 Jul 2019 14:34:11 -0700 (PDT)
MIME-Version: 1.0
From: Martin Duke <martin.h.duke@gmail.com>
Date: Mon, 08 Jul 2019 14:34:00 -0700
Message-ID: <CAM4esxQJGTjtD91XH1+oko4WS5HV-0yqSgvMaABb79SNN7nzUQ@mail.gmail.com>
Subject: Handshake timeout failures?
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007beda0058d32342c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Bmoc6mpl8GoMxOA7TEzToKo7Yrw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jul 2019 21:34:24 -0000

Is there somewhere in the drafts where we provide suggestions about how to
time out connections when not yet established? I believe the Idle Timeout
section applies specifically to established connections.

This need not be intensely prescriptive, but it would be nice to have some
guidelines on how not to fail too quickly.