IETF Logo Mail Archive

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

martinduke <notifications@github.com> Tue, 08 October 2019 23:46 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 50ADB1200DF for <quic-issues@ietfa.amsl.com>; Tue, 8 Oct 2019 16:46:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 WCi4b1_s7_BZ for <quic-issues@ietfa.amsl.com>; Tue, 8 Oct 2019 16:46:34 -0700 (PDT)
Received: from out-21.smtp.github.com (out-21.smtp.github.com [192.30.252.204]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7C5C1200D6 for <quic-issues@ietf.org>; Tue, 8 Oct 2019 16:46:33 -0700 (PDT)
Date: Tue, 08 Oct 2019 16:46:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1570578393; bh=gDya61U/glXV8SQiSvPPAllFNJvxMKgK1sxyxv5voJk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=AX4XzjS8ix6PKAtfoo//sr9m/jrfl2xpFdXG2ICMpyzXcXNCPmDr18UdnrdzKUXwL w6HBDCyaDSw88NbdYskXiggPaRtKGcFokX5w7ljnBqtLUFCjYwibakHGNCldbgs+iV TaJp9M+1UF8JGQXtufhSyv3WXZdSU5gv4p6FbFu0=
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4RDWBIOVK6EQBUZGF3VJQGREVBNHHB23NCOM@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/539750595@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_5d9d1fd8eaad3_4f993fdfe92cd964841ab"; 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/0AVVKTOIqI5yrnMU9aJ4DkCqJcw>
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, 08 Oct 2019 23:46:36 -0000

@janaiyengar It is the most straightforward way to send PTO and I see no downside, so yes.

That said, I know that many of our mechanisms (e.g. discarding keys) bake in assumptions about the handshake and who sends what and when, so maybe we should examine the implications of, for example, a client sending a Handshake PING before it gets any Handshake packets from the server.

-- 
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-539750595

v2.14.0 | Report a Bug | By Email