max_ack_delay for handshake
Martin Duke <martin.h.duke@gmail.com> Tue, 09 July 2019 16:59 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 94C88120294 for <quic@ietfa.amsl.com>; Tue, 9 Jul 2019 09:59: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 r2SvjzPqTizD for <quic@ietfa.amsl.com>; Tue, 9 Jul 2019 09:59:14 -0700 (PDT)
Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (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 DB68D1201AA for <quic@ietf.org>; Tue, 9 Jul 2019 09:59:13 -0700 (PDT)
Received: by mail-wm1-x329.google.com with SMTP id g67so4017414wme.1 for <quic@ietf.org>; Tue, 09 Jul 2019 09:59: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=gH+EAgxNtGh0n9eY7Do2K0Ay0UwE1bIkVDYjPxeIyRQ=; b=DJjfCd7zlSu4nAmo7jt13UkOZ0zEhwcq+mINVJuMV44qf3LWy2bASPDy7igm3tym34 GIBEh/HfGPhDMjmWYgZaV75WeBx+B3baoZsko1tfNRYmXocuQWi802A1z5EkERx4Jkgg t23tKZSBhvEG+uWaTAUplkECwlSnzVcABK1qeGfyPZz4FiXn5LMR7aO0NiPrsgmuwcm3 ow848kPvMncf+i4+94avBBWC3Tr1PPXTUHaX/iqv8rPpFLO6z7VoqzJ3iAGMXKT0t0cR CzFf7iUD7OeK2DNhFsHGHER7Y7vGFZuhDomOheiJFBOGheB06DJRid6wZ4iuot0LzR6N HfQg==
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=gH+EAgxNtGh0n9eY7Do2K0Ay0UwE1bIkVDYjPxeIyRQ=; b=fG8XsqDeX59BqsMHTgCPH4mG6VbR17QBa4jOot0RVbQzHk0gh0lBIN77ZcaDmko+8W rIc8wozjFl5sGsHEwiWMj0H289ICWJjZOFz1AbaeX2WC8RmSpczvDzU/l5DVNiopXcY5 6/F4jCSjuYUyUdhKLH4+E5SG3a4ij8W/wx0UViOYtmOOE4/Z/qUULzot9jjbraYTGBA4 027g6agNSO7L4do6Y17pcpId6iT5B7ptm26YlzN9UdgCzK+6qZJrhQ6SUUJWP3/SSDdC diKtr6wAUY1cTDWsdtdlhwQ66+0WjK/JFpZ75bq9507cy3yCbwnYehwnOO2Tewc8EJTa CGIA==
X-Gm-Message-State: APjAAAXaRhnBrq263iGO/sT8HRbOwxWH+/PTLvKJPPuEkbUyvvXoXa2M XSO0v3xib2fujI6Zvz6aLVWOXsdGtbmICJtNvjgn5Kqgyqw=
X-Google-Smtp-Source: APXvYqylfDyg/MB6ajBEEnbBjIY0llhE4Zkd8TnFg/SWhgz9JsFGE8nrsQOzSOAeidJmJdNqj3/r4OWfwseuu+2P1Lw=
X-Received: by 2002:a1c:67c3:: with SMTP id b186mr769529wmc.34.1562691552028; Tue, 09 Jul 2019 09:59:12 -0700 (PDT)
MIME-Version: 1.0
From: Martin Duke <martin.h.duke@gmail.com>
Date: Tue, 09 Jul 2019 09:59:00 -0700
Message-ID: <CAM4esxTLWNnKbzZNYq3QyWZfxMtdHtp74XoKMjRtnVy91UGuPw@mail.gmail.com>
Subject: max_ack_delay for handshake
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000da3004058d427a8b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/E8HRPfVAL3FkJmCImHtXa7OtM6s>
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: Tue, 09 Jul 2019 16:59:16 -0000
New to section 4.4 of quic-recovery; *For Initial and Handshake packets, a max_ack_delay of 0 is used.* I see two possible meanings of this: 1) endpoints MUST not intentionally delay acks of Initial and Handshake packets; 2) In RTT calculation, endpoints should assume a peer max_ack_delay of zero. (2) is a little hairy because there is one RTT estimate, not a per-context one. But what is the intent here?
- max_ack_delay for handshake Martin Duke
- Re: max_ack_delay for handshake Martin Duke