Discover and read the best of Twitter Threads about #quic
Most recents (4)
[1/š§µ] I believe @bob_way has already gone way overboard with #ILP and all the complexities of explaining all that needs to be expressed. ā¤ļø
Still, let me make a few remarks on the following topics š
ā¢ Infrastructure layers of #ILP
ā¢ #XRPL Payment Channels
ā¢ "Ledger Graphs"
Still, let me make a few remarks on the following topics š
ā¢ Infrastructure layers of #ILP
ā¢ #XRPL Payment Channels
ā¢ "Ledger Graphs"
[2/17] ā Infrastructure Layers of #Interledger ā
When it comes to the most recent version of the open #ILPv4 suite in universal mode (high volume, low value payments), the layering is as follows:
1ā£ Application
2ā£ Transport
3ā£ Interledger (Core Layer)
4ā£ Link
5ā£ Ledger
When it comes to the most recent version of the open #ILPv4 suite in universal mode (high volume, low value payments), the layering is as follows:
1ā£ Application
2ā£ Transport
3ā£ Interledger (Core Layer)
4ā£ Link
5ā£ Ledger
[3/17] ā 1ā£ Application Layer ā
This is the suite's first layer, and it contains the following protocol:
ā”ļø #SPSP (Simple Payment Setup Protocol)
š This is for #identifiers, which are comparable to email addresses and are used to make addresses readable.
This is the suite's first layer, and it contains the following protocol:
ā”ļø #SPSP (Simple Payment Setup Protocol)
š This is for #identifiers, which are comparable to email addresses and are used to make addresses readable.
Data and thoughts after enabling HTTP/3 at @Wix for our user domains #webperf #http3 #quic
Positive impact from TTFB to later phases such as FCP and LCP
1. TTFB p75 for CDN hits is considerably faster (~2x), especially in countries with weak devices or connections
Positive impact from TTFB to later phases such as FCP and LCP
1. TTFB p75 for CDN hits is considerably faster (~2x), especially in countries with weak devices or connections
2. Browser Adoption - Chrome/Firefox currently support the latest h3, Edge/Opera support h3-29
60% - 70% of requests are using HTTP/3 in Chromium based browsers (Chrome, Edge, Opera), and 40% of Firefox requests
Only 2% of Safari (experimental, will it be the default in iOS 15?)
60% - 70% of requests are using HTTP/3 in Chromium based browsers (Chrome, Edge, Opera), and 40% of Firefox requests
Only 2% of Safari (experimental, will it be the default in iOS 15?)
3. Session breakdown per protocol and browser for first page views tells a bit of a different story.
Only ~15%-20% of HTML requests are using HTTP/3
This can probably be explained by the connection upgrade behavior of the alt-svc header - first time visitors initially use h2
Only ~15%-20% of HTML requests are using HTTP/3
This can probably be explained by the connection upgrade behavior of the alt-svc header - first time visitors initially use h2
Day 4 of our deep dive into the freshly standardized #QUIC protocol is about one of its most innovative aspects: connection migration!
This is intended to allow #QUIC connections to survive network changes that are disruptive in TCP.
1/12 #RFC9000
This is intended to allow #QUIC connections to survive network changes that are disruptive in TCP.
1/12 #RFC9000
Take the "parking lot problem": you have WiFi on your phone inside, but switch to 4G when going to your car.
This switches networks and client IP/port, so all TCP connections are dropped and re-started, since they're only identified based on client+server IP+port (4-tuple). 2/12
This switches networks and client IP/port, so all TCP connections are dropped and re-started, since they're only identified based on client+server IP+port (4-tuple). 2/12
QUIC instead assigns each connection a unique Connection ID (CID) of 1-20 bytes.
By using the same CID even after switching networks, the server knows it's actually the same connection, even though the 4-tuple has changed. 3/12
By using the same CID even after switching networks, the server knows it's actually the same connection, even though the 4-tuple has changed. 3/12
I wrote a blog post looking at potential threats for #QUIC and HTTP/3 adoption and deployment calendar.perfplanet.com/2018/quic-and-ā¦. This will also be the basis for a talk at the HTTP symposium at curl-up in Prague at the end of March 2019 github.com/curl/curl-up/wā¦
Yesterday, there was a #QUIC workshop at the #conext18 conference with a large amount of new insights. Most of my notes on this can be found at docs.google.com/document/d/16Sā¦. Following tweets contain the parts relevant to the blogpost.
