@chris Apple's "iCloud Private Relay" has very peculiar requirements. For instance, your home server must support #QUIC: https://developer.apple.com/support/prepare-your-network-for-icloud-private-relay
Just to get this straight in my head: fundamentally, #Wireguard and #QUIC both support true #multihoming? 🫣
Also, both in a way support multiple concurrent "streams"? So if I take my glasses off, they look "the same"? 🤯
@jordanwhited how does tailscale/wireguard-go deal with flaky GSO support? The quic-go devs are currently racking their brains over it:
#networking #Linux #go #Golang #http3 #quic
Multiplexed Application Substrate over QUIC Encryption (masque)
@mike805 @profoundlynerdy Ever notice that #Google boosted the ranking of HTTPS sites at the same time they were pushing #QUIC, which eventually became the substrate for HTTP/3 and is coincidentally both easier to fingerprint and harder to scan and filter?
If #IPv6 had similar ad-boosting features I’m sure they’d be all over it.
</tinfoil-hat>
I've tied the last loose ends after #GPN21 .
My lightning talk was about using #SSH keys for #TLS connections, and I talked about the resulting prototype application.
Now I'm publishing quishka: a huge mess, but it proves that it can be done!
https://framagit.org/dcz/quishka
But why? Read the blog post for some context.
#GPN21 #ssh #tls #quic #rust #rustlang
Use Cases and Requirements for QUIC as a Substrate
https://www.ietf.org/archive/id/draft-kuehlewind-masque-quic-substrate-00.html
Still waiting to be able to use #QUIC :'(
(ie. do not want to have to use custom OpenSSL or whatever)
2 years after RFC 9000, here comes the sequel: RFC 9369 “#QUIC Version 2”.
“Note that "version 2" is an informal name for this proposal that indicates it is the second version of QUIC to be published as a Standards Track document. The protocol specified here uses a version number other than 2 in the wire image, in order to minimize ossification risks.”
Referenced link: https://twitter.com/i/web/status/1663566508755152896
Discuss on https://discu.eu/q/https://twitter.com/i/web/status/1663566508755152896
Originally posted by IoT For All / @iotforall: http://nitter.platypush.tech/iotforall/status/1663566508755152896#m
#ConnectedCars have the challenge of relaying important vehicle data in challenging network environments. Join @EMQTech for their upcoming webinar that presents a cutting-edge solution: #MQTT messaging over the #QUIC transport protocol. Learn how the combination of these two can… https://twitter.com/i/web/status/1663566508755152896
Bart van de Velde from Cisco talking about the emerging use of #QUIC at #RIPE86. In the next release of our free, #OpenSource #DNS resolver Unbound, we’ll offer support for DNS-over-QUIC. #DoQ https://github.com/NLnetLabs/unbound/pull/871
#quic #ripe86 #opensource #dns #DoQ
Some agenda highlights of SharkFest'23 US:
- #Wireshark and AI by Roland Knall
- Capturing #WiFi6E with Wireshark by Megumi Takeshita
- Kubeshark: The API Traffic Analyzer for #Kubernetes by Alon Gimonsky
- Dive into #DNS over #QUIC - DoQ by Betty DuBois
Join us next month in San Diego!
https://sharkfest.wireshark.org/sfus
#wireshark #WiFi6E #kubernetes #dns #quic
Quicssh: SSH over QUIC
Link: https://github.com/moul/quicssh
Discussion: https://news.ycombinator.com/item?id=35729260
FelixGaudin has developed a nice extension to #LibreSpeed that measures Responsiveness under working conditions (RPM) using #QUIC and #HTTP/3 try it on https://speedtest.rysingan.dev/
Referenced link: https://twitter.com/i/web/status/1646943545184362499
Discuss on https://discu.eu/q/https://twitter.com/i/web/status/1646943545184362499
Originally posted by IoT For All / @iotforall: http://nitter.platypush.tech/iotforall/status/1646943545184362499#m
📅 Quick! Book your spot for the Connected Vehicles webinar hosted by @EMQTech, showcasing how to use MQTT over #QUIC to meet the demands of next-generation connected vehicle services.
Register now 👉 || https://www.emqx.com/en/events/the-future-of-connected-vehicle-services
#connectedcars #connectedvehicles #mqtt #IoV… https://twitter.com/i/web/status/1646943545184362499
#quic #connectedcars #connectedvehicles #mqtt #IoV
Внимание, в последнем обновлении пакета Nginx с поддержкой QUIC протокола изменена логика работы параметра http3. Теперь для активации протокола HTTP/3 требуется предварительно активировать транспортный протокол QUIC через новый параметр quic.
#linux #nixos #nginx #quic #http3