SAM 3.2: Clarifications

SSU: Notes on RelayRequest

i2p2www/pages/site/docs/api/samv3.html

@@ -94,11 +94,13 @@ The following changes will be incorporated in the main part of this document soo
 <li>The server's control socket may optionally offer SSL/TLS support, as configured on the server and client.
     Implementations may offer other transport layers as well; this is outside the scope of the protocol definition.
 <li>For STREAM FORWARD, client may add SSL=true to use an SSL socket
-<li>New commands QUIT, STOP and EXIT will close the session and socket
+<li>New commands QUIT, STOP and EXIT will close the session and socket. Implementation is optional,
+    for ease in testing via telnet.
 <li>Command parsing will properly handle UTF-8
 <li>Command parsing reliably handles whitespace inside quotes
 <li>A backslash '\' may escape quotes on the command line
-<li>It is recommended but not required that the server map commands and option names to upper case.
+<li>It is recommended but not required that the server map commands to upper case, for ease in testing via telnet.
+    Do not map keys to upper case, as this would corrupt I2CP options.
 <li>Empty option values such as PROTOCOL or PROTOCOL= may be allowed, implementation dependent.
 <li>Servers may implement timeouts for the HELLO or subsequent commands, implementation dependent.
 </ul>

i2p2www/pages/site/docs/spec/ssu.html

@@ -657,6 +657,7 @@ use the packet's source address and port.
 This message may be sent via IPv4 or IPv6. If IPv6, Alice must include her IPv4 address and port.
 </li><li>
 If Alice includes her address/port, Bob may perform additional validation before continuing.
+Prior to release 0.9.24, Java I2P rejected any address or port that was different from the connection.
 </li><li>
 Challenge is unimplemented, challenge size is always zero
 </li><li>