IETF Logo Mail Archive

Re: [quicwg/base-drafts] Allow PING in Initial/Handshake? (#3034)

martinduke <notifications@github.com> Tue, 01 October 2019 20:14 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DFFF12006E for <quic-issues@ietfa.amsl.com>; Tue, 1 Oct 2019 13:14:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.281
X-Spam-Level:
X-Spam-Status: No, score=-6.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 jl-SAbAsp74Q for <quic-issues@ietfa.amsl.com>; Tue, 1 Oct 2019 13:14:24 -0700 (PDT)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D847612001E for <quic-issues@ietf.org>; Tue, 1 Oct 2019 13:14:23 -0700 (PDT)
Received: from github-lowworker-c5134a3.ac4-iad.github.net (github-lowworker-c5134a3.ac4-iad.github.net [10.52.23.55]) by smtp.github.com (Postfix) with ESMTP id D2F192C1525 for <quic-issues@ietf.org>; Tue, 1 Oct 2019 13:14:22 -0700 (PDT)
Date: Tue, 01 Oct 2019 13:14:22 -0700
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZHTV45SHDJQA7G46F3UD2C5EVBNHHB23NCOM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3034/537209381@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3034@github.com>
References: <quicwg/base-drafts/issues/3034@github.com>
Subject: Re: [quicwg/base-drafts] Allow PING in Initial/Handshake? (#3034)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d93b39ec29c9_780d3feffaacd968327185"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/r1058JTHkhhCKsqvDjCD63pB2FI>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Oct 2019 20:14:25 -0000

The case that I found interop was that my client and one packet's worth of unacknowledged data. In the 1-RTT case, I'd just send the data in the first probe and then a PING in the second probe.

Since I can't do that for Handshake, I have two unattractive options:
- send only one probe, reducing the probability of success
- introduce special logic to spread out the data into two packets with a CRYPTO frame (gross)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3034#issuecomment-537209381

v2.23.0 | Report a Bug | By Email