Re: [tcpm] TCP Connection ID

[Alexander Azimov <[e-mail]>]

Dear colleagues,

I haven't got any reply which increases level my confusion.

If there was no such proposal I will be glad to volunteer to write such a
document. But if you believe that such functionality is not needed in TCP -
I will be glad to learn your opinion in advance.

пт, 15 мая 2020 г. в 18:07, Alexander Azimov <[e-mail]>:

> Dear WG,
>
> As you all know L3 LB is a common element of today's cloud infrastructure.
> Its original design was based on the connection state that maps backend IPs
> (real IPs) to connection. Recently there were several papers that were
> suggesting the move to the stateless L3 LB, where the state (connection id)
> becomes the property of connection and it kept at the client, so the L3 LB
> can work without keeping state for every connection. As far as I
> understand, for QUIC it becomes native with destination connection ID in
> its header.
>
> I've seen suggestions for getting this functionality in TCP by overloading
> the Timestamps option or even TCP SEQ - can't say that such design looks
> good for me. I wonder was there an attempt to add connection id in the TCP
> options, and if it was - why it wasn't successful?
>
> --
> Best regards,
> Alexander Azimov
>


-- 
Best regards,
Alexander Azimov