Re: [quicwg/base-drafts] Describe a new version negotiation mechanism which allows for (#1755)

Kazuho Oku <notifications@github.com> Mon, 17 September 2018 21:15 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 BDE71130DD3 for <quic-issues@ietfa.amsl.com>; Mon, 17 Sep 2018 14:15:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.009
X-Spam-Level:
X-Spam-Status: No, score=-3.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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-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 HVxwCt9zc0xU for <quic-issues@ietfa.amsl.com>; Mon, 17 Sep 2018 14:15:14 -0700 (PDT)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 76D9B130E28 for <quic-issues@ietf.org>; Mon, 17 Sep 2018 14:15:14 -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=K1LGkYAkb6XrU/bemtPyGj9mvIU=; b=bfGfe6cgoJ0AA1bT YZkE07Q3hDsPga9znVK0Su7REKvJ792NwHWSLDM+tDPrFiALvE6neANnQeTtr+F3 ZufKyTqTfFsEB4GzivWf9ArcnkG4ql3+58eo/uaWr74lGB/EqrkzVV3O6v7HXN6M GwCcIh5Tv3dsqo7PCcmie8JtupQ=
Received: by filter0876p1las1.sendgrid.net with SMTP id filter0876p1las1-20610-5BA01961-16 2018-09-17 21:15:13.407715411 +0000 UTC m=+947943.175172414
Received: from github-lowworker-56a5eb2.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0018p1iad2.sendgrid.net (SG) with ESMTP id A5mlC4BhTQq2hI-RTX00oA for <quic-issues@ietf.org>; Mon, 17 Sep 2018 21:15:13.281 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-56a5eb2.cp1-iad.github.net (Postfix) with ESMTP id 33F28C0D3C for <quic-issues@ietf.org>; Mon, 17 Sep 2018 14:15:13 -0700 (PDT)
Date: Mon, 17 Sep 2018 21:15:13 +0000
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab3d107fbde84615937d137588878a36e2e1078ce092cf0000000117b7db6192a169ce1583704e@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1755/c422174161@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1755@github.com>
References: <quicwg/base-drafts/pull/1755@github.com>
Subject: Re: [quicwg/base-drafts] Describe a new version negotiation mechanism which allows for (#1755)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ba019612f004_40603f9f8f0d45bc629534"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1JOIhC0oUus4x1qEHzsmt3HIjDSZ6H4hBx8l 2a40e/OAfAKDPonvRtG2ZRagF+nm/qkOwRad6vqPFGLrIfhQ04y7FUqj3lK/Q44+PlBQIw8e0Ll/I1 Gm1OWzArVCZJvdg8B1fnULMPQ8GwvSJTlxanwl3mzi7N6FOlIgF2WZdbR5feO59RT6IGeRIhR6F1VS 0=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/cN6KZFduThzbV1jyMkVs1TpRYxw>
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, 17 Sep 2018 21:15:18 -0000

@RyanAtGoogle 
> I'm not sure that I understand what constraints on the two versions are required in order to allow this approach to work.

FWIW, my assumption is that the only constraint would be that the TLS protocol version needs to be compatible.

Consider the case where you want to send a QUICv1 Initial packet that can be upgraded to v3. From the Initial packet, the v3 server needs to extract the initial flight of the TLS handshake (i.e. ClientHello) and the elements that would have existed in the v3's Initial packet. It is obvious that the TLS handshake transcript can be extracted. The other elements can be transmitted as a TLS ClientHello extension.

-- 
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/1755#issuecomment-422174161