# Handshake Handshake is a decentralized naming and certificate-authority protocol that uses a blockchain to manage DNS top-level-domain registration, renewal, and transfer. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Nginx TLS tuning for HTTPS performance, TTFB, and latency DevFeed: [Nginx TLS tuning for HTTPS performance, TTFB, and latency]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-06-10T12:06:18Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [nginx](), [TLS (Transport Layer Security)](), [Latency](), [Handshake](), [HTTP](), [Back end]() Tags: [blog](), [encryption](), [http](), [http-3](), [latency](), [linux](), [nginx](), [performance](), [request](), [reuse](), [security](), [server](), [sysadmins](), [tls]() ### AI overview A practical guide to tuning Nginx TLS, HTTP/2, and HTTP/3 settings for HTTPS performance. It explains that tuning can reduce handshake overhead and improve connection reuse, while application execution often remains the main contributor to TTFB and latency. ### Source excerpt Nginx TLS tuning won't fix a slow application, but it does cut handshake overhead and improve connection reuse, which shaves milliseconds off every HTTPS request. Continue reading... ## How TCP Handshake Works DevFeed: [How TCP Handshake Works]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-03-31T08:17:52Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [Handshake](), [client](), [servers]() Tags: [client](), [communication](), [http-3](), [quic](), [sequence](), [server](), [tcp](), [tcp-handshake]() ### AI overview A tutorial explaining the TCP three-way handshake. It describes how a client sends SYN, a server responds with SYN-ACK, and the client completes the connection with ACK, including the role of initial sequence numbers and control flags. ### Source excerpt The 3 step process ## IS-IS 3-Way Handshake and the Power of SHOULD DevFeed: [IS-IS 3-Way Handshake and the Power of SHOULD]() Original publisher: [Read original article]() Published: 2025-07-01T06:17:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [IS-IS](), [Cisco](), [Internet Engineering Task Force (IETF)](), [Handshake]() Tags: [cisco](), [download](), [ietf](), [is-is](), [standard](), [standards]() ### AI overview The article explains why Cisco's pre-standard IS-IS 3-way handshake can interoperate with RFC 5303 implementations. It attributes this to RFC 5303 making some TLV 240 fields optional, while Cisco's IETF handshake includes additional fields that can be validated when present. ### Source excerpt Yesterday, I mentioned that a Cisco router running pre-standard IS-IS 3-way handshake (this is why you need it) interoperates with multiple implementations of RFC 5303. How's that possible, and does it matter whether you configure the ancient Cisco routers (release 15.x) to use IETF 3-way handshake instead of the "proprietary" one? TL&DR: It SHOULD NOT matter, but the more I explore the RFCs, the more I'm amazed anything works at all. I took a trip to the Wireshark land to figure out the details (you can download the capture file): Read more ... ## Lab: Configure IS-IS on Point-to-Point Links DevFeed: [Lab: Configure IS-IS on Point-to-Point Links]() Original publisher: [Read original article]() Published: 2024-10-22T06:24:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [IS-IS](), [networking](), [Handshake](), [Ethernet]() Tags: [ethernet](), [is-is](), [netlab](), [networking](), [ospf]() ### AI overview A lab exercise on configuring IS-IS for point-to-point links in Ethernet networks. It compares IS-IS with OSPF, explains the differences between point-to-point and multi-access links, and introduces the three-way handshake. ### Source excerpt From a very high-level perspective, OSPF and IS-IS are quite similar. Both were created in the Stone Age of networking, and both differentiate between multi-access LAN segments and point-to-point serial interfaces. Unfortunately, that approach no longer works in the Ethernet Everywhere world where most of the point-to-point links look like LAN segments, so we always have to change the default settings to make an IGP work better. That's what you'll do in today's lab exercise, which also explains the behind-the-scenes differences between point-to-point and multi-access links and the intricate world of three-way handshake. Read more ... ## Forge: Enabling TLS 1.3 DevFeed: [Forge: Enabling TLS 1.3]() Original publisher: [Read original article]() Author: Mohamed Said Published: 2020-10-20T15:27:00Z Content type: release Language: en Sources: [Laravel Blog]() Topics: [TLS (Transport Layer Security)](), [Handshake](), [Laravel](), [Ubuntu](), [Server]() Tags: [laravel](), [servers](), [tls](), [ubuntu](), [upgrade]() ### AI overview Laravel Forge servers running Ubuntu 20.04 now enable TLS 1.3 by default for newly issued Let's Encrypt certificates. TLS 1.3 provides a faster handshake and more secure cipher suites; existing certificates must be reissued and activated to receive the upgrade. ### Source excerpt As of today, newly issued LetsEncrypt certificates on Laravel Forge servers that run on Ubuntu 20.04 have TLS 1.3 enabled by default. TLS 1.3 offers a faster handshake and more secure cipher suites....