23 Nov
2018
23 Nov
'18
11:22 a.m.
Some of us had recently been talking about Layer 2 vs. Layer 3 roaming.
Well, it looks like HTTP/3 is basically a TCP replacement on top of UDP,
and it allows a connection to continue between IP address changes by using
a per-connection UUID.
https://blog.erratasec.com/2018/11/some-notes-about-http3.html
We can expect this to be implemented, at the very least, in the most
popular web browsers but possible other programs as well.
This could really mitigate the issues with non-roaming capable mesh
networks.
--
marc/juul
23 Nov
23 Nov
12:13 p.m.
I'm wondering how the ssl fiasco like how http/2.0 problem is avoided in this,
i'll read the notes when i get home.
Thanks,
Jared Null
On Nov 23, 2018, at 11:22 AM, Marc Juul
<marc(a)juul.io> wrote:
Some of us had recently been talking about Layer 2 vs. Layer 3 roaming.
Well, it looks like HTTP/3 is basically a TCP replacement on top of UDP, and it allows a
connection to continue between IP address changes by using a per-connection UUID.
https://blog.erratasec.com/2018/11/some-notes-about-http3.html
<https://blog.erratasec.com/2018/11/some-notes-about-http3.html>
We can expect this to be implemented, at the very least, in the most popular web browsers
but possible other programs as well.
This could really mitigate the issues with non-roaming capable mesh networks.
--
marc/juul
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://sudoroom.org/lists/listinfo/mesh
3:05 p.m.
I think it's confusing to think of these as HTTP versions. HTTP is actually
staying pretty much the same (with maybe minor modifications). It may be
more helpful to think of HTTP/2 as HTTP-over-SPDY, and HTTP/3 as
HTTP-over-QUIC, where SPDY and QUIC are TCP replacements.
Why replace TCP? Pretty much only because of the latency of opening a TLS
connection. SPDY was implemented on top of TCP, with a clever handshake and
support for multiplexing, etc. It seems that to get higher performance
Google has decided to use UDP.
As for roaming, I don't see how the problem is changed. You still need to
give your roaming client an IP address (even if you're using QUIC).
Alex
Στις Παρ, 23 Νοε 2018 στις 11:23 π.μ., ο/η Marc Juul <marc(a)juul.io> έγραψε:
Some of us had recently been talking about Layer 2 vs.
Layer 3 roaming.
Well, it looks like HTTP/3 is basically a TCP replacement on top of UDP,
and it allows a connection to continue between IP address changes by using
a per-connection UUID.
https://blog.erratasec.com/2018/11/some-notes-about-http3.html
We can expect this to be implemented, at the very least, in the most
popular web browsers but possible other programs as well.
This could really mitigate the issues with non-roaming capable mesh
networks.
--
marc/juul
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://sudoroom.org/lists/listinfo/mesh
9:53 p.m.
On Fri, Nov 23, 2018 at 3:05 PM Alexander Papazoglou <papazoga(a)gmail.com>
wrote:
I think it's confusing to think of these as HTTP
versions. HTTP is
actually staying pretty much the same (with maybe minor modifications). It
may be more helpful to think of HTTP/2 as HTTP-over-SPDY, and HTTP/3 as
HTTP-over-QUIC, where SPDY and QUIC are TCP replacements.
Why replace TCP? Pretty much only because of the latency of opening a TLS
connection. SPDY was implemented on top of TCP, with a clever handshake and
support for multiplexing, etc. It seems that to get higher performance
Google has decided to use UDP.
I'm not sure how much this entered into their thinking but UDP has the
advantage that there are tricks available to traverse NATs. This might make
decentralized web apps easier to implement though I guess we'll have to see
what makes it into the browsers.
As for roaming, I don't see how the problem is
changed. You still need to
give your roaming client an IP address (even if you're using QUIC).
Supposedly QUIC connections will stay open while switching IP addresses.
Alex
Στις Παρ, 23 Νοε 2018 στις 11:23 π.μ., ο/η Marc Juul <marc(a)juul.io>
έγραψε:
Some of us had recently been talking about Layer
2 vs. Layer 3 roaming.
Well, it looks like HTTP/3 is basically a TCP replacement on top of UDP,
and it allows a connection to continue between IP address changes by using
a per-connection UUID.
https://blog.erratasec.com/2018/11/some-notes-about-http3.html
We can expect this to be implemented, at the very least, in the most
popular web browsers but possible other programs as well.
This could really mitigate the issues with non-roaming capable mesh
networks.
--
marc/juul
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://sudoroom.org/lists/listinfo/mesh
2013
days inactive
2014
days old
3 comments
3 participants
participants (3)
-
Alexander Papazoglou -
Jared Null -
Marc Juul