--- a/rvinterf/localsock.h	Sat Nov 23 20:15:02 2013 +0000
+++ b/rvinterf/localsock.h	Sat Nov 23 22:15:16 2013 +0000
@@ -5,9 +5,8 @@
  * The UNIX domain sockets used for this ad hoc interface are of the
  * SOCK_STREAM kind, but the true nature of the communication is message-based.
  * We use the same trick that is used for DNS over TCP: every message in each
- * direction is preceded by a 2-byte length.  This length and all other
- * multibyte numbers are sent in the native byte order of the machine on which
- * the rvinterf suite is running.  The limit on the size of these messages
+ * direction is preceded by a 2-byte length.  This length is sent MSB first
+ * just like in DNS over TCP.  The limit on the size of these messages
  * (for sizing buffers etc) is:
  */
 
@@ -29,12 +28,11 @@
  * interested in receiving copies of certain packets coming from the target.
  *
  * The CLI2RVI_WANT_RVTRACE opcode needs to be followed by a USEID mask value
- * and a USEID match value, both in the native byte order of the machine
- * running rvinterf, for a total message length of 9 bytes.  For every RV
- * trace message received from the target, rvinterf will iterate through all
- * active clients to see who is interested: if the received USEID ANDed with
- * the mask equals the match value, the message will be forwarded to that
- * client.
+ * and a USEID match value, both in the network byte order, i.e., MSB first,
+ * for a total message length of 9 bytes.  For every RV trace message received
+ * from the target, rvinterf will iterate through all active clients to see who
+ * is interested: if the received USEID ANDed with the mask equals the match
+ * value, the message will be forwarded to that client.
  *
  * The CLI2RVI_WANT_MUXPROTO opcode needs to be followed by one byte
  * identifying the RVTMUX protocol of interest, i.e., the first byte of the