Going Peer to Peer with QUIC
Marten Seemann and I just published an entry on his blog, A p2p Vision for QUIC. This is a technical argument, explaining how a series of small improvements to the QUIC standards would suffice to make QUIC a great peer-to-peer (P2P) protocol. I personally love it, because the Internet suffers greatly from excessive centralization, with big platforms acting as gatekeepers. Currently, pretty much all user activities on the Internet are mediated by “services in the cloud”. Take for example something as simple as a security camera in your home. People want to check the camera images when they are outside the home. They cannot connect to the camera or even a home server directly, because the home network is “behind a NAT” – and very possibly behind multiple layers of NAT, given the scarcity of IPv4 addresses. The practical solution is to export the images from the camera to a “service in the cloud”, and to let user contact that service from their cellphone. It works, but it has obvious issues for privacy, security, or even continuity of service: if the cloud service stops, the camera gets bricked. The proposed QUIC architecture would provide a generic solution using the Masque standard for relaying QUIC, combine with QUIC NAT traversal extensions to migrate connections from “using the relay” to “directly P2P”, as shown in the following diagram. +------------------------------+ | Step 1: phone contacts | v the camera through +---|---+ +-----------+-+ the relay | Phone | | Masque ^ | +---|---+ | Relay | | | +-----------|-+ +-------------------------+ | | Step 2: phone and camera cooperate +-----|----|-+ and establish a "hole" in the NAT. | NAT | | | +-----|----|-+ Step 3: traffic flows directly | | between phone and camera without +-|----|-+ burdening the relay | Camera | +--------+ The standards to achieve that are almost ready. The relaying of incoming connections is described in the UDP Listen, already adopted in the Masque Working Group. A draft submitted to the IETF QUIC Working Group describes the Using QUIC to Traverse NAT, and another describes QUIC Address Discovery. I have already implemented the Address Discovery draft in picoquic, and intend to promptly implement the other two drafts. Using QUIC has many advantages. The communications are encrypted end to end, even when they are going through the relay, which has nice security and privacy benefits. The relay is uses standards and is not dependent on the application; if a relay goes out of business, just pick another one. In the weird cases where the NAT traversal fails, the application still works. There are of course many more applications of P2P possible, such as for example direct video calls between two homes, video games and more. The vision is clear: we can do all those applications using QUIC.
Flock + AI-powered cameras - staffny
I think we all by now understand that AI (artificial intelligence) is not the solution when it comes to understanding humans. It often makes errors, and when yo...
Everything I own, owned
Turning Claude loose on the firmware of five USB and WiFi peripherals, and finding a command shell in a microphone, a defeatable webcam activity LED, and unauthenticated memory writes over the network.
Event Cameras: a New Way of Sensing - Davide Scaramuzza - ICCP 2024 Keynote
Apple Vision Pro
Featuring the new powerful M5 chip and comfortable Dual Knit Band, Apple Vision Pro seamlessly blends digital content with your physical space.
IPFS as a first-class citizen in FFmpeg, who’s next?
The first steps in enabling IPFS support in the wider open source ecosystem.
Running an Open Source Home Area Network
Insights on running a Home Area Network (HAN) nearly completely on open source software, including configurations and metrics.
Camo Studio - Stand out video with any camera
Camo enables the camera you already own to produce incredible video, whether you’re meeting, streaming, or recording. Start creating great video today.
Standard for the transmission of IP datagrams on avian carriers
This memo describes an experimental method for the encapsulation of IP datagrams in avian carriers. This specification is primarily useful in Metropolitan Area Networks. This is an experimental, not recommended standard.
GitHub - iptv-org/iptv: Collection of publicly available IPTV channels from all over the world
Collection of publicly available IPTV channels from all over the world - iptv-org/iptv
Iran built a vast camera network to control dissent. Israel turned it into a targeting tool
Israel’s use of Tehran street cameras to help kill Iran’s supreme leader shows how everyday surveillance can turn into a wartime weapon.
An Update on OpenTitan
proto IM | AIM-inspired video chat for the open web
Free video calls and buddy lists built on the AT Protocol. Like FaceTime, but it works on every device. Works with Blacksky, Bluesky, or any atproto account.
Thingino: The open-source firmware for IP cameras based on Ingenic SoCs.