IETF Logo Mail Archive

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

hardie <notifications@github.com> Mon, 19 March 2018 13:47 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 EFC9F126D74 for <quic-issues@ietfa.amsl.com>; Mon, 19 Mar 2018 06:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.392
X-Spam-Level:
X-Spam-Status: No, score=-0.392 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_24=1.618, 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=no 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 JQ72QDf4RG79 for <quic-issues@ietfa.amsl.com>; Mon, 19 Mar 2018 06:47:33 -0700 (PDT)
Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 E49E01242F5 for <quic-issues@ietf.org>; Mon, 19 Mar 2018 06:47:32 -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=oJSs6uUNeu2K/5aXlV6MT5Vubz4=; b=TOHAFqsDJ8c6jPoL Zjm2MhxdVdPoiLGm5cAxVylO2cCieoy2pIL4PCH4uVnVa2gBaO2CXNh8HISEF9Nc K6uF373N2BrrM+Tt0nffpGz0aq7EXsRvjXlgZy48I9O4Wp+Ji3RaFKaU1lefofVU IMYyFK1NR6jWQTGgEI4QHvt1LeE=
Received: by filter0584p1iad2.sendgrid.net with SMTP id filter0584p1iad2-13538-5AAFBF73-29 2018-03-19 13:47:31.697720382 +0000 UTC
Received: from smtp.github.com (out-5.smtp.github.com [192.30.252.196]) by ismtpd0015p1iad2.sendgrid.net (SG) with ESMTP id RBvr-OiGSfGqWi25ZqXqWg for <quic-issues@ietf.org>; Mon, 19 Mar 2018 13:47:31.605 +0000 (UTC)
Date: Mon, 19 Mar 2018 13:47:31 +0000
From: hardie <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4638e024d68ad5c5d068b970176bc0ab9b4bb5bc92cf0000000116c7817392a169ce0defbdad@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/374217104@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_5aafbf73758d9_35d12b0a4162ced0147983"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: hardie
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak20zwpVaLgVDOX1rz8vdwFfc7PY8K5pY9hoka 0aH8uyureNuhmingVDi7R7cppQxPLhaHdbDrcFTA+4PAeWJEauJJxSd0mL6BlTO2j/QKeGgZFlO6hp r6vPxnoanQYT2dz5wq2nn5HlsrkZhyeMyJsTk0orKygLLFNg3ZWLFCqwdw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/I6E7U29KNlXHC7HH8NqsSWLmxto>
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:47:34 -0000

It seems like supplying the connection ID with the session ticket allows you to both use the same one for all session tickets supplied (the same as this proposal) or to vary them with session ticket supplied which might be useful in some routing contexts.  Could we consider that approach as well?

-- 
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-374217104

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