IETF Logo Mail Archive

Re: [quicwg/base-drafts] Multiple connections on the same port (#714)

Igor Lubashev <notifications@github.com> Wed, 09 August 2017 22:39 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 4803E13239B for <quic-issues@ietfa.amsl.com>; Wed, 9 Aug 2017 15:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level:
X-Spam-Status: No, score=-2.019 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_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 O0xc9tTlGXzT for <quic-issues@ietfa.amsl.com>; Wed, 9 Aug 2017 15:39:47 -0700 (PDT)
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 620A7132380 for <quic-issues@ietf.org>; Wed, 9 Aug 2017 15:39:47 -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=nSMR/VYH94FbEaD1bBe0XLv8ynA=; b=f+UXTM+PP5tQUWPN A9cGBXlpnHJnmo4jKZ9SrLmJaoU+ExHKEOSO0BCkT7SK5nFCwn8XVrV0APeGDAkh plu1Eoq6kAES64D6HAnKXM99TC1Gg9s5qzCCm0DjwV7OlG6ikQw36TkMMKmyjFes YVEhNIAEWcewkBXH37Q/6GPtoJw=
Received: by filter1145p1mdw1.sendgrid.net with SMTP id filter1145p1mdw1-2322-598B8F32-2B 2017-08-09 22:39:46.443392893 +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 ismtpd0027p1mdw1.sendgrid.net (SG) with ESMTP id D_5kSudeQ-qczQTLuDTYTg for <quic-issues@ietf.org>; Wed, 09 Aug 2017 22:39:46.398 +0000 (UTC)
Date: Wed, 09 Aug 2017 22:39:46 +0000
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc104ab86c6a918c44b6d30ad478a5bf3647a06cb92cf0000000115a3513292a169ce0ed5746a@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/714/321400931@github.com>
In-Reply-To: <quicwg/base-drafts/issues/714@github.com>
References: <quicwg/base-drafts/issues/714@github.com>
Subject: Re: [quicwg/base-drafts] Multiple connections on the same port (#714)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_598b8f321c802_5be13f93547fbc38304a2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2ITH+AClF8owL2WP4SywH2SuInmLWJvS7cKo uQcZ1h0MV6WBkId+yMO6A4TlsL276/xxBQwqlCvBRA3a6d0rvdvXkxNi04b06rn0LJYKQNER0GD5K/ AUrv16RTO2238APFcrdcU3xQNTjNuA2k4gJFQXK8jnvhB0Tg6xIJG440RUUxrcGcwJJ3K+taZlK9zx w=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/9lctGjGii4Ma8DsXW_W3NzatK70>
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: Wed, 09 Aug 2017 22:39:49 -0000

So the server's first 1-RTT packet would have client's connection ID and carry server's connection ID in transport params.  But all subsequent server's packets will have server's connection ID?  (Or will all subsequent server's packets still have client's connection ID, while client's 1-RTT packets will have Server's connection ID?)

In the former case (only the server's first 1-RTT packet has client's connection ID), what happens if that first packet is lost/reordered?  Will the client respond with a Stateless Reset, when it receives server's second 1-RTT packet with server's connection ID?

-- 
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/714#issuecomment-321400931

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