IETF Logo Mail Archive

Re: [quicwg/base-drafts] 0-RTT can't use transport parameters or 1-RTT frames (#2461)

Kazuho Oku <notifications@github.com> Wed, 13 February 2019 21:59 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 DE39012D4EA for <quic-issues@ietfa.amsl.com>; Wed, 13 Feb 2019 13:59:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.001
X-Spam-Level:
X-Spam-Status: No, score=-8.001 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_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 heKB2S3uR9oL for <quic-issues@ietfa.amsl.com>; Wed, 13 Feb 2019 13:59:24 -0800 (PST)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D07AD128766 for <quic-issues@ietf.org>; Wed, 13 Feb 2019 13:59:23 -0800 (PST)
Date: Wed, 13 Feb 2019 13:59:22 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1550095162; bh=IGxxXaVMqtwJGmDupty5TrGxb8IMpCwhf3WS/Es8zXM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tosgFO5binbW8uRslYV5L3gJPfzxguEgOJ2WyGF9FpbpAvakx66Rzzb9WhgYxrink 2pThLV8Krv03oGEVSInwj9RyNq0CsQPdOxowPiZjxRfUuO/Qg0cgmACfvcX/ZpBnWx k8DyDtnx3drLGVZnqxRSkQkJBNbIIyZsQr1IuPTY=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe448a1d95fe678c490528dfbc79514180a3ed3e992cf00000001187c553a92a169ce1869fe88@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2461/c463392078@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2461@github.com>
References: <quicwg/base-drafts/pull/2461@github.com>
Subject: Re: [quicwg/base-drafts] 0-RTT can't use transport parameters or 1-RTT frames (#2461)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c64933a5dc33_484c3f7ff1ad45c0825f4"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/lNOUAFHYkhvpwXRv5ICL6SDLba8>
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, 13 Feb 2019 21:59:26 -0000

@ianswett 
> I think this is ok, but I think it's going to be difficult to get this correct in practice. I expect most implementations will migrate to 1-RTT keys as soon as possible and try to avoid writing special logic for this case, but I can't come up with a way to force clients to do that.

I think it's possible. I think that's what the PR is trying to suggest is that a server can:
* enforce limits based on TP to streams-related frames sent using 0-RTT packets (see #2461)
* refuse to handle any of the following frames in a 0-RTT packet: ACK, PATH_RESPONSE, RETIRE_CONNECTION_ID (see #2458)


-- 
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/pull/2461#issuecomment-463392078

v2.23.0 | Report a Bug | By Email