IETF Logo Mail Archive

Re: [quicwg/base-drafts] Prime client with connection ID for 0-RTT (#584)

ekr <notifications@github.com> Mon, 19 March 2018 13:49 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 8AD0212D95E for <quic-issues@ietfa.amsl.com>; Mon, 19 Mar 2018 06:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 8dnVZCBoWbNk for <quic-issues@ietfa.amsl.com>; Mon, 19 Mar 2018 06:49:01 -0700 (PDT)
Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40A6B12DA1D for <quic-issues@ietf.org>; Mon, 19 Mar 2018 06:48:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Ntel9dm1xcip8E3mWCXqsi3vloo=; b=jMpCaPkjJNMdbCbL 4VZ3zL06jsBhUYcj7m8a7sl0sjuZUh8zXfozjD4GAsLI5+DiVY2OVoztJILcUjPW m4ot9Ql1WAdLcXlsPlKlQtC42mpvDLkkjVXngEUoQY80SErPMdGjnTjEfjIAjItE bTNT2B4nrHKS951LkVqiOOdsXog=
Received: by filter0265p1iad2.sendgrid.net with SMTP id filter0265p1iad2-6731-5AAFBFB6-41 2018-03-19 13:48:38.55736647 +0000 UTC
Received: from smtp.github.com (out-3.smtp.github.com [192.30.252.194]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id SRGSp-G3QVuEMQ9WqhRLlA for <quic-issues@ietf.org>; Mon, 19 Mar 2018 13:48:38.186 +0000 (UTC)
Date: Mon, 19 Mar 2018 13:48:38 +0000
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab0ec02f93766f5c21fbc5ae2e62341e68a59df0bd92cf0000000116c781b692a169ce0defbdad@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/584/374217442@github.com>
In-Reply-To: <quicwg/base-drafts/issues/584@github.com>
References: <quicwg/base-drafts/issues/584@github.com>
Subject: Re: [quicwg/base-drafts] Prime client with connection ID for 0-RTT (#584)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5aafbfb613f6f_10d03f8b5c098f2c2886f2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1KJ69/ffl3sgU67tVWTe14w7nkxsvq/eFs8A eRlFL3+JINkchaewWROYDOTluO6InOV1LCcEbJIIlYkRgSSMxruqmBHgQ/vAeZL71i3VcRERLpnE7V DLKCIWSowbkQzk0onmNFl50/LX6+CaUrlQLAFOqqxHJLNjdAC/1xAXrKEA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/jQEwCYx6mQRfLXxpAt-xfMWmrT4>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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, 19 Mar 2018 13:49:05 -0000

I think it's a reasonable idea in concept, but I'm not super-enthusiastic about the proposed newSessionTicket frame. As a practical matter, you're going to need your TLS stack to process the NST, so I'd rather just send it in stream/cream 0 and then have the TLS stack eat it. At that point you have two options:

1. Internal session cache, in which you interrogate the TLS stack after it has emitted CH (but before you send the packet) for its properties (whether 0-RTT is available, ALPN, etc.)
2. External session cache, in which the TLS stack tells you when a new ticket is available and its properties and you store it.

-- 
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/584#issuecomment-374217442

v2.39.1 | Report a Bug | By Email | System Status