IETF Logo Mail Archive

Re: [quicwg/base-drafts] Crypto Frames/Packets Aren't Blocked by CC (#2377)

ianswett <notifications@github.com> Mon, 28 January 2019 23:01 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 23D3D130EE4 for <quic-issues@ietfa.amsl.com>; Mon, 28 Jan 2019 15:01:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.552
X-Spam-Level:
X-Spam-Status: No, score=-12.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 QTuj-nTopM4f for <quic-issues@ietfa.amsl.com>; Mon, 28 Jan 2019 15:01:14 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A299C131239 for <quic-issues@ietf.org>; Mon, 28 Jan 2019 15:01:11 -0800 (PST)
Date: Mon, 28 Jan 2019 15:01:10 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1548716470; bh=1YHAKk5BjgPCQFi6XdL65uEVbJfGrqrkpuT48S3xl/o=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QHnWLZY7L+JXsZMH4Kbe8jkRkrvbILJc394snONXRqjcP/DPj77HGcv4r1lEe2j96 /boVmyo78gcaULpsqV1c+gZu0iVmMj6BPpA+ELDZK0oAxgV8jPr3VYcOgJsxqGeBCa iPmPg6W6o7267LzPenmlkWgn7H63nlBQYYqeS7Lc=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb488f63f7416f01e9cbc7450a8d65bb4eb3fdb1292cf0000000118674bb692a169ce180fd1a3@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2377/458337059@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2377@github.com>
References: <quicwg/base-drafts/issues/2377@github.com>
Subject: Re: [quicwg/base-drafts] Crypto Frames/Packets Aren't Blocked by CC (#2377)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c4f89b689efa_6dd93f8a9dad45b41880ac"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/sY1qu3BKy8ZCK_ooL86PqPVMZX4>
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: Mon, 28 Jan 2019 23:01:18 -0000

In most cases, even with 0-RTT responses, you'd send the crypto data before 1-RTT data, so the crypto data wouldn't be blocked by congestion control.

I think the interesting case is what if the crypto data is large(ie: >IW10)?  It seems like congestion control should probably apply there?

gQUIC did ensure crypto packets were never blocked by congestion control, so I suspect this was in the docs early on, but has subsequently removed.  I suspect it was rarely if ever a practical issue in our implementation, but it is a bit easier to reason about if CRYPTO frames are always sent immediately.

-- 
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/2377#issuecomment-458337059

v2.23.0 | Report a Bug | By Email