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

Mike Bishop <notifications@github.com> Tue, 08 August 2017 22:55 UTC

Date: Tue, 08 Aug 2017 22:55:20 +0000
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab875c6e0a8af8fd1fa99173c1fed2f0bafe620c3f92cf0000000115a2035792a169ce0ed5746a@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@github.com>
Subject: [quicwg/base-drafts] Multiple connections on the same port (#714)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_598a4157f05fe_f733fd346303c3010437c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/8JMBiNGfqBN7qKMVCIcR6dZP1RY>

@mikkelfj has raised questions about whether we might be able to maintain many connections on the same port.  @ianswett has pointed out that other connection-ID-oriented protocols operate *all* connections on the same port to minimize the use of ephemeral ports.  However, if any of those connections are to the same back end, there will be duplicate 5-tuples, and QUIC's current model doesn't support simultaneous handshakes with the same 5-tuple.

If we want to enable this, we would need to have the server's first flight continue using the client-chosen Connection ID, but contain the new 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

[quicwg/base-drafts] Multiple connections on the … Mike Bishop
Re: [quicwg/base-drafts] Multiple connections on … janaiyengar
Re: [quicwg/base-drafts] Multiple connections on … Igor Lubashev
Re: [quicwg/base-drafts] Multiple connections on … Igor Lubashev
Re: [quicwg/base-drafts] Multiple connections on … Mike Bishop
Re: [quicwg/base-drafts] Multiple connections on … janaiyengar
Re: [quicwg/base-drafts] Multiple connections on … Igor Lubashev
Re: [quicwg/base-drafts] Multiple connections on … janaiyengar
Re: [quicwg/base-drafts] Multiple connections on … Igor Lubashev
Re: [quicwg/base-drafts] Multiple connections on … janaiyengar
Re: [quicwg/base-drafts] Multiple connections on … MikkelFJ
Re: [quicwg/base-drafts] Multiple connections on … Martin Thomson
Re: [quicwg/base-drafts] Multiple connections on … MikkelFJ
Re: [quicwg/base-drafts] Multiple connections on … Martin Thomson
Re: [quicwg/base-drafts] Multiple connections on … MikkelFJ
Re: [quicwg/base-drafts] Multiple connections on … Nick Banks
Re: [quicwg/base-drafts] Multiple connections on … MikkelFJ
Re: [quicwg/base-drafts] Multiple connections on … Nick Banks
Re: [quicwg/base-drafts] Multiple connections on … MikkelFJ
Re: [quicwg/base-drafts] Multiple connections on … Nick Banks
Re: [quicwg/base-drafts] Multiple connections on … MikkelFJ
Re: [quicwg/base-drafts] Multiple connections on … Nick Banks
Re: [quicwg/base-drafts] Multiple connections on … MikkelFJ
Re: [quicwg/base-drafts] Multiple connections on … Nick Banks
Re: [quicwg/base-drafts] Multiple connections on … MikkelFJ
Re: [quicwg/base-drafts] Multiple connections on … Nick Banks
Re: [quicwg/base-drafts] Multiple connections on … MikkelFJ
Re: [quicwg/base-drafts] Multiple connections on … ianswett
Re: [quicwg/base-drafts] Multiple connections on … Nick Banks
Re: [quicwg/base-drafts] Multiple connections on … MikkelFJ
Re: [quicwg/base-drafts] Multiple connections on … ianswett
Re: [quicwg/base-drafts] Multiple connections on … MikkelFJ
Re: [quicwg/base-drafts] Multiple connections on … martinduke
Re: [quicwg/base-drafts] Multiple connections on … Martin Thomson
Re: [quicwg/base-drafts] Multiple connections on … Martin Thomson
Re: [quicwg/base-drafts] Multiple connections on … MikkelFJ