search
TCP
Trends
- 1Lessons Learned from Developing Internet Protocols●Leveraging Lessons Learned Developing Internet Protocols
Communications of the ACM has published a feature examining lessons learned from decades of developing internet protocols. The piece reflects on how early design decisions in protocols like TCP and IP shaped today's internet, and what those experiences teach engineers building new networking standards. It comes as the technical community debates protocol design for emerging areas such as the next generation of internet architecture.
- 2Routing LLM traffic across providers with TCP-style congestion control▼Routing LLM traffic across inference providers with TCP-style congestion control
Engineers are discussing a proposal to route large language model inference traffic across multiple providers using congestion control methods borrowed from TCP. The approach dynamically shifts requests toward faster or more reliable providers, similar to how internet protocols manage network congestion. Commenters see it as a practical answer to inconsistent latency and availability across AI inference services.
- 3
A new write-up explores running PostgreSQL over the QUIC protocol instead of the usual TCP connection. QUIC, developed originally at Google and standardized by the IETF, promises faster connection setup, built-in encryption and better performance on unreliable networks. The project is drawing attention from database and infrastructure developers curious whether these transport-layer gains translate into real-world improvements for database traffic.
- 4TDengine vulnerability lets unauthenticated packets crash servers●🤖 CVE-2026-42542 (CVSS 7.5): integer underflow in TDengine's pre-auth RPC message parsing. A single crafted packet to TC
A new vulnerability, CVE-2026-42542 with a CVSS score of 7.5, has been disclosed in TDengine, an open-source time-series database used in OT and IoT deployments. The flaw is an integer underflow in pre-authentication RPC message parsing: a single crafted packet sent to TCP port 6030 can crash unauthenticated servers. Versions 3.4.0.0 through 3.4.1.5 are affected, with a fix released in version 3.4.1.6. No exploitation in the wild has been reported so far, and a proof-of-concept has been withheld.