aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDimitri Staessens <dimitri@ouroboros.rocks>2022-12-07 22:20:34 +0100
committerDimitri Staessens <dimitri@ouroboros.rocks>2022-12-07 22:20:34 +0100
commit8d39895ee24ce004cebd91dffa464e00263dd1e4 (patch)
tree44f7b5323cee95fac033c460746d496e3985a499
parent84c6cf1980da5cb749657425b99419d80ffc0d15 (diff)
downloadwebsite-8d39895ee24ce004cebd91dffa464e00263dd1e4.tar.gz
website-8d39895ee24ce004cebd91dffa464e00263dd1e4.zip
blog: Fix some typos in loc-id post
-rw-r--r--content/en/blog/20221207-loc-id-split.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/content/en/blog/20221207-loc-id-split.md b/content/en/blog/20221207-loc-id-split.md
index 8c2a068..6544837 100644
--- a/content/en/blog/20221207-loc-id-split.md
+++ b/content/en/blog/20221207-loc-id-split.md
@@ -7,7 +7,7 @@ author: Dimitri Staessens
A few weeks back I had a drink with a Thijs who is now doing a
master's thesis on Loc/Id split, so we dug into the concepts behind
-Locators and Identifiers and see if matches or in anyway interferes
+Locators and Identifiers and see if matches or in any way interferes
with the Ouroboros network model.
For this, we started from the paper _Locator/Identifier Split
@@ -19,11 +19,11 @@ In a nutshell, Loc/Id split starts from the observation that the
transport layer (TCP, UDP) is tightly coupled to network (IP)
addresses via a certain TCP/UDP port.
-Assuming our IPv4 local address is 10.10.0.1/24 and there is an SSH
-server on 10.10.5.253/24 listening on port 22, after making a
-connection, our client application could be bound to 10.10.0.1/24 on
+Assuming our IPv4 local address is 10.10.0.1 /24 and there is an SSH
+server on 10.10.5.253 /24 listening on port 22, after making a
+connection, our client application could be bound to 10.10.0.1 /24 on
port 25406. If we move our laptop to another room that is on an access
-point in a different subnet, and we receive IP address 10.10.4.7/24,
+point in a different subnet, and we receive IP address 10.10.4.7 /24,
our TCP connection to the SSL server will break.
Loc/Id split suggest to split the "address" into two parts, an
@@ -72,7 +72,7 @@ to some SSH server, but this time we're in a Loc/Id split network. So
my laptop got a different address for its interface, an identifier,
say COFF33D00D, and, since I'm in the green network, a locator that is
conveniently the IPv4 address for my wireless LAN interface,
-10.10.0.1/24. The TCP connection in the SSH client is Loc/Id aware,
+10.10.0.1 /24. The TCP connection in the SSH client is Loc/Id aware,
and now bound to C0FF33D00D:25406. After connecting to the client at
008BADF00D, It learns that I'm C0FF33D00D and my locator is 10.10.0.1.