IETF Logo Mail Archive

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

janaiyengar <notifications@github.com> Thu, 10 August 2017 18:31 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 96AE2132406 for <quic-issues@ietfa.amsl.com>; Thu, 10 Aug 2017 11:31:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.595
X-Spam-Level:
X-Spam-Status: No, score=-0.595 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, SPF_PASS=-0.001, 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 kChdCpDZpCNr for <quic-issues@ietfa.amsl.com>; Thu, 10 Aug 2017 11:31:08 -0700 (PDT)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 21B721323B1 for <quic-issues@ietf.org>; Thu, 10 Aug 2017 11:31:08 -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=GrjQiL7kb/DkMsviBeOgExr0Wr0=; b=QcVz6qRQuJ6d8bUU 0Udv68bFV6gOuPUO9f7qsU+w4Jjj6v3LLK5OaApRoDOHZOZyqjluYyHvUWCtknVB LLsPDhn42mD79xvhF77AbkYTZRSC6ekb8YqW/zejlfRt1HTxCUFKNlkzy/8QCFCh 6BLf4PCSf6cX07N9qAXFNdALfYA=
Received: by filter0441p1mdw1.sendgrid.net with SMTP id filter0441p1mdw1-1484-598CA66A-22 2017-08-10 18:31:06.382018066 +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 ismtpd0031p1mdw1.sendgrid.net (SG) with ESMTP id 2WTNrHMDSCWtrVeZ06Rh-w for <quic-issues@ietf.org>; Thu, 10 Aug 2017 18:31:06.365 +0000 (UTC)
Date: Thu, 10 Aug 2017 18:31:06 +0000
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf1e2da38df964bc25035f565473a5a9874e9e10d92cf0000000115a4686a92a169ce0ed5746a@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/321635782@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_598ca66a1295b_137d3fc6db9f1c306937d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2GCNs5BZKk5kKpATjL9jsCj4NJjvhXZJ6xvv CDc/dFu0g7dHKceQsX9VpFceb8/+inTTkkZAbZ/W/5/4Qpb4BzIcRgs/POZQUnL3LSKLyAAZZseJzh JBd/s2uRlPO+AimOPKH+5sYULXVl8UwHp2TWSb37NnU6U4Mcr01np39XiiGuK6rLKLNgPCNmhr2BT+ w=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/FnSJb95gzfKF3O7V9sLF3sAGZU4>
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: Thu, 10 Aug 2017 18:31:09 -0000

Good point. In this case, the client would have to maintain a shared buffer for undecrypted packets that arrive on the socket but cannot be assigned to a connection yet, or some such logic. That seems fine as the responsibility of a client that is choosing to multiplex connections over the same 5-tuple.

As for Stateless Reset, that is only sent by the server, and the connection ID is clear in that case.

-- 
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-321635782

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