[quicwg/base-drafts] Version negotiation might never terminate (#1919)

MikkelFJ <notifications@github.com> Thu, 25 October 2018 21:41 UTC

Date: Thu, 25 Oct 2018 14:41:31 -0700
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2bfdcf8825c8561086fa9c1be90f1885559ad98c92cf0000000117e9fa8b92a169ce164cfd01@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1919@github.com>
Subject: [quicwg/base-drafts] Version negotiation might never terminate (#1919)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bd2388beea04_7f133fe21cad45c415063d2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/vhpkS2mYBm-jgiTOcAYX-RJyLK8>

facts:
client does not support version C but does support A and B.
server X and Y are exposed as two separate IP addresses on the same domain.
client always chooses the next IP round robin when sending and initial packet nr.0.
server X supports version B, C
server Y supports version A, C

scenario
forever {
client sends Initial packet in version A and server X responds with vneg B, C
client sends Initial packet in version B and server Y responds with vneg A, C
}


-- 
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/1919

[quicwg/base-drafts] Version negotiation might ne… MikkelFJ
Re: [quicwg/base-drafts] Version negotiation migh… MikkelFJ
Re: [quicwg/base-drafts] Version negotiation migh… MikkelFJ