From 0c3e740b6a7e2083748788a11730514397b1d4af Mon Sep 17 00:00:00 2001 From: zzz Date: Sun, 17 Oct 2021 07:48:30 -0400 Subject: [PATCH] Prop. 159 markdown fixes take 3 --- i2p2www/spec/proposals/159-ssu2.rst | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/i2p2www/spec/proposals/159-ssu2.rst b/i2p2www/spec/proposals/159-ssu2.rst index 305334cf..a4c3431e 100644 --- a/i2p2www/spec/proposals/159-ssu2.rst +++ b/i2p2www/spec/proposals/159-ssu2.rst @@ -1220,7 +1220,7 @@ Use of IPv6 Flow Label and Migration `````````````````````````````````````````` QUIC recommends endpoints that send data using IPv6 SHOULD apply an IPv6 flow label -in compliance with [RFC6437]_, unless the local API does not allow +in compliance with [RFC-6437]_, unless the local API does not allow setting IPv6 flow labels. Unfortunately, the Java API does not allow setting IPv6 flow labels. @@ -2136,7 +2136,7 @@ We rely on several existing protocols, both within I2P and outside standards, for inspiration, guidance, and code reuse: * Threat models: From NTCP2 [NTCP2]_, with significant additional threats - relevant to UDP transport as analyzed by QUIC [RFC9000]_ [RFC9001]_. + relevant to UDP transport as analyzed by QUIC [RFC-9000]_ [RFC-9001]_. * Cryptographic choices: From [NTCP2]_. @@ -2146,15 +2146,15 @@ for inspiration, guidance, and code reuse: * Handshake ephemeral key obfuscation: Adapted from [NTCP2]_ -* Packet headers: Adapted from WireGuard [WireGuard]_ and QUIC [RFC9000]_ [RFC9001]_. +* Packet headers: Adapted from WireGuard [WireGuard]_ and QUIC [RFC-9000]_ [RFC-9001]_. * Packet header obfuscation: Adapted from [NTCP2]_ -* Packet header protection: Adapted from QUIC [RFC9001]_ and [Nonces]_ +* Packet header protection: Adapted from QUIC [RFC-9001]_ and [Nonces]_ * Headers used as AEAD associated data as in [ECIES]_. -* Packet numbering: Adapted from WireGuard [WireGuard]_ and QUIC [RFC9000]_ [RFC9001]_. +* Packet numbering: Adapted from WireGuard [WireGuard]_ and QUIC [RFC-9000]_ [RFC-9001]_. * Messages: Adapted from [SSU]_ @@ -2582,7 +2582,7 @@ the source router hash and IV are used. Header Protection ``````````````````` In addition to obfuscation, bytes 8-15 of the long header and bytes 8-12 of the short header -are encrypted by XORing with a known key, as in QUIC [RFC9001]_ and [Nonces]_. +are encrypted by XORing with a known key, as in QUIC [RFC-9001]_ and [Nonces]_. For SessionCreated, where the destination router hash and IV are not yet known, the source router hash and IV are used. @@ -4238,7 +4238,7 @@ RelayRequest blk :: 7 size :: 2 bytes, big endian, size of data to follow relay tag :: 4 byte relay (introduction) tag, nonzero, as received by - Alice in the SessionCreated_ message from Bob + Alice in the SessionCreated message from Bob asz :: 1 byte IP address size Alice IP :: Alice's IP address, network byte order, asz bytes APort :: 2 byte port number of Alice, network byte order @@ -4896,10 +4896,10 @@ This is crude and greatly reduces the efficiency. Continuing this feature in SSU 2 is TBD. Recent studies [PMTU]_ suggest that a minimum for IPv4 of 1200 or more would work -for more than 99% of connections. QUIC [RFC9000]_ requires a minimum IP +for more than 99% of connections. QUIC [RFC-9000]_ requires a minimum IP packet size of 1280 bytes. -quote [RFC9000]_: +quote [RFC-9000]_: The maximum datagram size is defined as the largest size of UDP payload that can be sent across a network path using a single UDP @@ -5247,6 +5247,7 @@ Padding is mod-16 padding for SSU 1 only. SSU 1 +================== =========== ===== ====== ======= ====== ===== Message Header+MAC Keys Data Padding Total Notes ================== =========== ===== ====== ======= ====== ===== Session Request 40 256 5 3 304 Incl. extended options @@ -5261,6 +5262,7 @@ Total 2254 SSU 2 +================== =========== ===== ====== ======= ====== ===== Message Header+MAC Keys Data Padding Total Notes ================== =========== ===== ====== ======= ====== ===== Session Request 48 32 7 87 DateTime block