diff options
| author | Dimitri Staessens <dimitri@ouroboros.rocks> | 2020-05-02 15:12:25 +0200 |
|---|---|---|
| committer | Dimitri Staessens <dimitri@ouroboros.rocks> | 2020-05-02 15:12:25 +0200 |
| commit | adf9b2cab7b64b22c15fc494584dece43e65c023 (patch) | |
| tree | d209a6698106a34e6335f1f59c96af422319003c | |
| parent | 8b2068b8c1ae19c817793f50adf63c4b9321b83e (diff) | |
| download | website-adf9b2cab7b64b22c15fc494584dece43e65c023.tar.gz website-adf9b2cab7b64b22c15fc494584dece43e65c023.zip | |
content: Fix network byte order
| -rw-r--r-- | content/en/blog/news/20200502-frcp.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/en/blog/news/20200502-frcp.md b/content/en/blog/news/20200502-frcp.md index 094565e..28c5794 100644 --- a/content/en/blog/news/20200502-frcp.md +++ b/content/en/blog/news/20200502-frcp.md @@ -233,4 +233,4 @@ Dimitri [^1]: Don't you love standards? One of the key design objectives for Ouroboros is exactly to avoid such shenanigans. Modify/abuse a header and Ouroboros should reject it because it _cannot work_, not because some standard says one shouldn't do it. [^2]: Lesser known fact: Gigabit Ethernet has a 512 byte minimum frame size; but _carrier extension_ handles this transparently. -[^3]: As you have figured out, the loopback is not in _network byte order_.
\ No newline at end of file +[^3]: In _network byte order_.
\ No newline at end of file |