Last revised: October 12, 2004

GO-Globals Protocol, RXP Overview

Proprietary

: The RXP protocol is a proprietary protocol used for all GO-Global client-server
data communications.
: Utilizes 3 different levels of compression.

Adaptive Tuning

: Designed and optimized to handle low-bandwidth connectivity.
: Detect bandwidth connection (UNIX only)
: Adjust mouse compression interval (UNIX only)
: Adjust flushing data interval before writing packets (UNIX only)
: Turns host backbuffer on (slow) or off (fast) (UNIX only)

Data port

: By default, the RXP protocol runs over TCP port 491 but it can be made to
run over any compatible data port.
: For specific port information see http://www.iana.org/assignments/port-
numbers or http://www.isecom.org/mirror/oprp.htm
: Operates as part of the standard TCP/IP protocol stack

Encryption & Security

: RXP is currently designed to handle encryption levels from 40-bit DES to 256-
bit AES & RSA. The encryption algorithm is GraphOn's implementation of the
Data Encryption Standard (DES) and Advanced Encryption Standard (AES).
The specification of the standard is available
at http://www.itl.nist.gov/fipspubs/fip46-2.htm.
: Given the proprietary nature of RXP, it is highly unlikely data can be
intercepted and interpreted without the use of a corresponding GO-Global
client.
:
Characteristics

: The RXP display protocol is almost entirely asynchronous. This means the
server and the client are never waiting for a response from its peer. For
example:
: The client sends a messages: The mouse moved here, a key was pressed (or
released), a mouse button was pressed (or released)
: The server only sends messages as follows: Draw rectangle(s) at a location,
put this image on the screen, draw this text, etc.
: The only "roundtrips" (i.e. synchronous requests) are when the server needs
the screen contents (this happens only during a rare occasion) or when the
server needs the client capabilities (screen size, etc). This only happens at
session startup. (UNIX only)
: A web server on the other hand handles all requests as synchronous (e.g.
the browser issues a "get web page", waits for response, the server sends
the web page, the browser receives and displays the web page).
: The protocol behaves much like any interactive stream-based protocol. It can
be treated like telnet or SSH.
: High latency is generally more harmful that low throughput.
Last revised: October 12, 2004
Network Connection Requirements

GO-Global for UNIX
: Minimum 28.8 Kbps modem speed
: 16 Kbps per user network bandwidth
: TCP/IP as a network protocol
: GO-Global listens on registered TCP/IP port 491
: GO-Global listens on registered TCP/IP port 791 for SSL connections
: Round trip network latency: <= 500ms. (High latency impacts
responsiveness, but usable to 500ms roundtrip)

GO-Global for Windows
: Minimum 28.8 Kbps modem speed
: 16 Kbps per user network bandwidth
: TCP/IP as a network protocol
: GO-Global listens on registered TCP/IP port 491.
: Round trip network latency: <= 300ms. (High latency impacts
responsiveness, but usable to 500ms roundtrip)