Re: [quicwg/base-drafts] Invariant: the first packet on a connection uses the long header (#1040)
ianswett <notifications@github.com> Tue, 09 January 2018 20:50 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 05B05126BFD for <quic-issues@ietfa.amsl.com>; Tue, 9 Jan 2018 12:50:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.625
X-Spam-Level:
X-Spam-Status: No, score=-0.625 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_28=1.404, 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, 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 2G7NWU19vonI for <quic-issues@ietfa.amsl.com>; Tue, 9 Jan 2018 12:50:19 -0800 (PST)
Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 6FA70126BF6 for <quic-issues@ietf.org>; Tue, 9 Jan 2018 12:50:19 -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=v6BqF4/GawRXnHvKp28em20Vnb4=; b=W6ACF3O1pzwh3Weo V77hpEt91w7Cx2VjscfPkmvpKuY8tslxS5pUVvSsItZ67b+O/UnE4qD9vE3qDKlG m4F44BZlvcKWsmX+qnq5Vz5T7fyZRfFeT16lvGXyPyB1I6WO0wDuj2XFAz1Jxsfr 2BMKA52uQ9BLWUkm604WVbvXe/M=
Received: by filter0029p1las1.sendgrid.net with SMTP id filter0029p1las1-23193-5A552B0A-9 2018-01-09 20:50:18.396257835 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0017p1iad2.sendgrid.net (SG) with ESMTP id 1IcQ6ZOSQOGrckf-AiYBRQ for <quic-issues@ietf.org>; Tue, 09 Jan 2018 20:50:18.283 +0000 (UTC)
Date: Tue, 09 Jan 2018 20:50:18 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1fb7d8aab93980e24a82e371c34f1836bac6e24492cf00000001166ced0a92a169ce111a9845@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1040/356409850@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1040@github.com>
References: <quicwg/base-drafts/issues/1040@github.com>
Subject: Re: [quicwg/base-drafts] Invariant: the first packet on a connection uses the long header (#1040)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a552b0a2d5a4_2cef3f8da9fd4f2810295a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0Cq/RzsqtygH7X8mGVqkzzTLbBFuJb2IpBkC Aj7Lz3TUVo2iviGQltyFIl/AQKwOytmMvYBy0muXGvx6u93n70QjnG+iBPqyhvmfAqs523EISgjXIx FlX4StkSuNcZYUMkUc+J2YCOOqEW0BlcOh0m9mYBziILNJ3VOzwvVHYsSq1uansIxgaxlUNeuALhAk E=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/-t_Dm_r3O8FCwE0vX-wE-44nSck>
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, 09 Jan 2018 20:50:21 -0000
In order for this not to be true, that implies you have done out of band version negotiation and key negotiation? At that point, I would call it migration rather than a new connection. One use case is to migrate a connection from a TLS 1.3 TCP connection to a QUIC connection. A similar use might be WebRTC using QUIC? It seems like we could do these no matter what we decide here. -- 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/1040#issuecomment-356409850
- [quicwg/base-drafts] Invariant: the first packet … Martin Thomson
- Re: [quicwg/base-drafts] Invariant: the first pac… Mike Bishop
- Re: [quicwg/base-drafts] Invariant: the first pac… ianswett
- Re: [quicwg/base-drafts] Invariant: the first pac… Martin Thomson
- Re: [quicwg/base-drafts] Invariant: the first pac… Martin Thomson
- Re: [quicwg/base-drafts] Invariant: the first pac… Martin Thomson
- Re: [quicwg/base-drafts] Invariant: the first pac… Mike Bishop