IETF Logo Mail Archive

[quicwg/base-drafts] Explain extraordinary conditions that lead to sending a Handshake packet (#2598)

Martin Thomson <notifications@github.com> Tue, 09 April 2019 22:32 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 03AB1120355 for <quic-issues@ietfa.amsl.com>; Tue, 9 Apr 2019 15:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level:
X-Spam-Status: No, score=-6.597 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 26e94P2gJA6j for <quic-issues@ietfa.amsl.com>; Tue, 9 Apr 2019 15:32:13 -0700 (PDT)
Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2108012034D for <quic-issues@ietf.org>; Tue, 9 Apr 2019 15:32:13 -0700 (PDT)
Date: Tue, 09 Apr 2019 15:32:12 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1554849132; bh=igi1qkGGURZqixqZLd3PBlGmmlMhzEoOig7uqTvYnH4=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=ry5VDy9EEW81upm2KLh59uZAxA3l3Yr3J8tzbHB2MbtMaeCJzcyrpLmQ5ziRJQiKg KfP28IJRacftB24SwDgwXsJg3XvZmS7zRMlA8Dg7ihWfxSkUGd3AaV1ubJWCk0Jdph Q+sIzHoSeCMFv1d98ZWH/DYRgNbk1lCXEyn8yPh8=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab8c0e97bda7394f7d0d248dac3be03688485ce8a192cebaba4fec92a169ce19b3f86d@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2598@github.com>
Subject: [quicwg/base-drafts] Explain extraordinary conditions that lead to sending a Handshake packet (#2598)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cad1d6ca2369_44483fceea8d45c01115d2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/fc5usOCsoh_RslGhnSGZBd9ehm8>
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, 09 Apr 2019 22:32:15 -0000

We don't provide examples of the weird cases where you need to send Handshake packets to prevent amplification deadlock.  The strangest one is where the client has all Initial data (and therefore has Handshake keys), but never receives a Handshake packet from the server.  In this case, the client needs to send a Handshake packet that won't contain ACK or CRYPTO frames.  We should explain this in a note.

See #2597.

-- 
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/2598

v2.23.0 | Report a Bug | By Email