IETF Logo Mail Archive

Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)

MikkelFJ <notifications@github.com> Mon, 05 February 2018 13:03 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 AE75412D77E for <quic-issues@ietfa.amsl.com>; Mon, 5 Feb 2018 05:03:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.029
X-Spam-Level:
X-Spam-Status: No, score=-2.029 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 jrQRzuNQ5ciZ for <quic-issues@ietfa.amsl.com>; Mon, 5 Feb 2018 05:03:49 -0800 (PST)
Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 BBC9A12D7E6 for <quic-issues@ietf.org>; Mon, 5 Feb 2018 05:03:46 -0800 (PST)
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=inhOzDcDoMpYJe9R72qqXgfEd7k=; b=E9l1cddPGvYb+z/+ t+0cm2Y1JFicDULW44EmmVuzqcWakKYsLSoRwKQBWkT8GaiVSrqy/cFmWTlpdQNQ NQ951z3NsUSFa8DOvwyIf+J65dJLtmG7IYgoauXgK061mEAfT8DedjZAUy4BxG1K sXQNL5z3FwRfTQOGowSrrd8Toco=
Received: by filter0356p1las1.sendgrid.net with SMTP id filter0356p1las1-12811-5A785631-D 2018-02-05 13:03:45.603852159 +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 ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id d_r8y4h6TiykfkbVSfW_jw for <quic-issues@ietf.org>; Mon, 05 Feb 2018 13:03:45.360 +0000 (UTC)
Date: Mon, 05 Feb 2018 13:03:45 +0000
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2d66d019e3cb6322d6d23041006438d01c0e16c692cf000000011690183192a169ce0c118d76@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/203/363078581@github.com>
In-Reply-To: <quicwg/base-drafts/issues/203@github.com>
References: <quicwg/base-drafts/issues/203@github.com>
Subject: Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a78563140b63_11fa3ff690d86f283664e"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2QHC7c7xO1rY0GeRBXSUGX2BWWsOK33rtdlp XP7wUOB44MLYHJhaaIYmjQJzPilXiDbD6L0Ck2MSHnrFBzfYykg9bsAIxB4vEhL5ewaolgLARRCT7f SiVA/GPY2NXWjtr8NDuQVsd2HwSgTGdreF/6r+1GOPPOWUV3JUD1qlwXxuxoBR5hCYXOr2ejsLxXNh o=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Rz9-wbhJMsJr4QiAJnigQRKXiso>
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, 05 Feb 2018 13:03:50 -0000

> Another option is to have a signal that notifies the start of using a new path. In such case, we should expose 1 bit that can be used to distinguish start-of-use vs. in-use. I am not sure if we need (or want to) expose the internals of the handshake (i.e. INITIAL, HANDSHAKE, RETRY).

This somewhat relates to the retry concern of asymmetric CID's
https://github.com/quicwg/base-drafts/issues/1089

-- 
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/203#issuecomment-363078581

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