[quicwg/base-drafts] Probe packet section needs to suggest a crypto context (#3074)

martinduke <notifications@github.com> Wed, 02 October 2019 20:19 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 0FB7F120018 for <quic-issues@ietfa.amsl.com>; Wed, 2 Oct 2019 13:19:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.353
X-Spam-Status: No, score=-6.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_20=1.546, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 6FaVWjbl64tE for <quic-issues@ietfa.amsl.com>; Wed, 2 Oct 2019 13:19:18 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92E8112002F for <quic-issues@ietf.org>; Wed, 2 Oct 2019 13:19:18 -0700 (PDT)
Received: from github-lowworker-f144ac1.va3-iad.github.net (github-lowworker-f144ac1.va3-iad.github.net []) by smtp.github.com (Postfix) with ESMTP id 8A035960784 for <quic-issues@ietf.org>; Wed, 2 Oct 2019 13:19:17 -0700 (PDT)
Date: Wed, 02 Oct 2019 13:19:17 -0700
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7D6RXYLEBUCFTMNV53UJDNLEVBNHHB3Z3HXI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3074@github.com>
Subject: [quicwg/base-drafts] Probe packet section needs to suggest a crypto context (#3074)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d9506457b009_733f3f88a60cd960109494"; 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/FrH8Qnplik0wNJlXa95PsVTtn-c>
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: Wed, 02 Oct 2019 20:19:21 -0000

Sec 5.3.1 of quic-recovery discusses how to send loss probes. Now that this can be done at any crypto level, there ought to be some suggestions (are any MUSTs needed) on what crypto level to send probes at.

This is probably like the CONNECTION_CLOSE suggestion; if you have multiple levels, it may be good to coalesce some packets.

I'm working through the logic and may have some suggestions soon.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: