Re: [quicwg/base-drafts] Invert the connection ID logic during the handshake (#442)
MikkelFJ <notifications@github.com> Tue, 25 April 2017 20:46 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 C72051294B2 for <quic-issues@ietfa.amsl.com>; Tue, 25 Apr 2017 13:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.8
X-Spam-Level:
X-Spam-Status: No, score=-4.8 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, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 o0d-AmmK5-ts for <quic-issues@ietfa.amsl.com>; Tue, 25 Apr 2017 13:46:10 -0700 (PDT)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 6602212709D for <quic-issues@ietf.org>; Tue, 25 Apr 2017 13:46:09 -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=UKMzs7A/JD6OFBidccaouTKOaXM=; b=RRUAsWCIch8ks8G3 fgO+2Q/BNagGbG1Z9Esm9VvfJnbJa1Dv7LSFDrxDCf50PjsN/NDsPqRNkaMQvZMo NqrnJWeVkjlc/VcYNyArvukqqbKzDUkA2JG8bWbV8Ep2kqQ8HdU7Q8skyRPj7yVn FvGdfm5RQmahlmDa1vZc0qxQJ4c=
Received: by filter0537p1mdw1.sendgrid.net with SMTP id filter0537p1mdw1-16321-58FFB57B-3C 2017-04-25 20:45:47.502385122 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id _EaP5ZKcTqusarI2i0VrUw for <quic-issues@ietf.org>; Tue, 25 Apr 2017 20:45:47.628 +0000 (UTC)
Date: Tue, 25 Apr 2017 13:45:47 -0700
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abecdbcb7096fead146f7863d26eece0cd9965afd092cf000000011517777b92a169ce0d441b68@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/442/297159564@github.com>
In-Reply-To: <quicwg/base-drafts/issues/442@github.com>
References: <quicwg/base-drafts/issues/442@github.com>
Subject: Re: [quicwg/base-drafts] Invert the connection ID logic during the handshake (#442)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58ffb57b7ca66_32eb3ff0b564dc38137550"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0YHR48mWNvoDBERVxbb0y1LFcSoBq8HZQPvp +HvetNP8DPCrHd/0CiAqbS/y0s+dQrIpuP2/KSfJLD8tg0NOGuKr/2YC78BnFR3GMMK35+3OdONZNA kNmsDZofPo/jiaj7tpcop4Wb64nE/Iglw0PAVZS+Lp0mLig/1Fp7khCDVrvIZEZrMUdD0aSdRSBIWd s=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/pgcK9L2YJrjXzScuDR5BG-oM3sI>
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: Tue, 25 Apr 2017 20:46:12 -0000
Perhaps I am missing something fundamental, but If a stream is set up during 0rtt or clear text, the stream cannot continue once the client id changes to server id if loadbalancers route traffic elsewhere when the id is updated. All the state machinery won't work. It's fine to have stateless setup, but then it needs to a UDP oriented approach such that streams and retransmissions are removed during this phase and replaced with a simpler retry until success. For example, periodically sent ClientHello until ServerFinal is received, and there would be no ServerNonFinal because that is stateful. ServerNonFinal is problematic regardless because it is not ordered by a stream, so this makes structuring the handshake rather complex. For 0RTT the entire point is to start early - so here the routing needs to reach a stateful server early. But then again, as long as replay attacks are not solved for 0RTT, they have limited. -- 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/442#issuecomment-297159564
- [quicwg/base-drafts] Invert the connection ID log… Martin Thomson
- Re: [quicwg/base-drafts] Invert the connection ID… MikkelFJ
- Re: [quicwg/base-drafts] Invert the connection ID… MikkelFJ
- Re: [quicwg/base-drafts] Invert the connection ID… janaiyengar
- Re: [quicwg/base-drafts] Invert the connection ID… Igor Lubashev
- Re: [quicwg/base-drafts] Invert the connection ID… Martin Thomson
- Re: [quicwg/base-drafts] Invert the connection ID… Brian Trammell
- Re: [quicwg/base-drafts] Invert the connection ID… martinduke
- Re: [quicwg/base-drafts] Invert the connection ID… Martin Thomson
- Re: [quicwg/base-drafts] Invert the connection ID… Martin Thomson