From 1dcd6135e6252a542ab94ddf40cce42e9571a746 Mon Sep 17 00:00:00 2001 From: Max Inden Date: Thu, 27 Jan 2022 15:16:27 +0100 Subject: [PATCH] src/_blog: Link to referenced papers --- src/_blog/libp2p-hole-punching.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_blog/libp2p-hole-punching.md b/src/_blog/libp2p-hole-punching.md index 9a79dac3..565239b2 100644 --- a/src/_blog/libp2p-hole-punching.md +++ b/src/_blog/libp2p-hole-punching.md @@ -61,7 +61,7 @@ Now this should not suggest to go ahead and disable all firewalls across the wor Hole punching is one mechanism to overcome the problem described above. Let's see how it works. -Imagine that we have some mysterious mechanism to synchronize *A* and *B*. Mysterious as synchronizing clocks is hard, … really hard. For those that don't believe me, I recommend reading Lamport's "Time, Clocks, and the Ordering of Events in a Distributed System" and Mills' "A Brief History of NTP Time: Memoirs of an Internet Timekeeper". +Imagine that we have some mysterious mechanism to synchronize *A* and *B*. Mysterious as synchronizing clocks is hard, … really hard. For those that don't believe me, I recommend reading Lamport's [_Time, Clocks, and the Ordering of Events in a Distributed System_](https://web.archive.org/web/20211101121036/https://amturing.acm.org/p558-lamport.pdf) and Mills' [_A Brief History of NTP Time: Memoirs of an Internet Timekeeper_](https://web.archive.org/web/20220120075303/https://www.eecis.udel.edu/~mills/database/papers/history.pdf). Anyways, back to assuming the existence of a mysterious synchronization mechanism. Such mechanism would allow *A* and *B* to dial each other "at the same time".