minor felinet change

proto/felinet.proto

@@ -11,13 +11,13 @@ service Handler {
 message LoginRequest {
     string username = 1;
     string password = 2;
+    bytes uuid = 3;
 }
 
 message LoginResponse {
     bool success = 1;
     uint32 error = 2;
     string msg = 3;
-    bytes uuid = 4;
 }
 
 message PacketIn {

standard.tex

@@ -719,9 +719,13 @@ FELINET nodes communicate with each other via gRPC. A FELINET server implements
 \item In $CallsignFilter.ssid$, the valid values are 0-255, like in all other SSIDs. Protobuf does not have a fixed single-byte type, so a uint32 is used instead. If an invalid value is supplied, the server must reject it, and close the stream.
 \end{itemize}
 
+\subsection{State}
+
+FELINET servers require some amount of state tracking. This is done by passing a V4 UUID into every request. The client is responsible for generating this UUID.
+
 \subsection{Authentication}
 
-FELINET defines a $Login$ endpoint, which is meant to be used for authentication. The exact usage of this endpoint is up to the server. For example, it may be used to allow any access, it may be used to allow write access, or it may even blindly accept all credentials. This endpoint is meant to be as flexible as possible. The $Login$ endpoint returns a UUID, which must be passed into future requests. This UUID is used to track state.
+FELINET defines a $Login$ endpoint, which is meant to be used for authentication. The exact usage of this endpoint is up to the server. For example, it may be used to allow any access, it may be used to allow write access, or it may not be used at all. This endpoint is meant to be as flexible as possible.
 
 \subsection{Filtering}