client
Click on the red underlined text to get to the source
... SSL supports mutual authentication of both the client and server
using signed digital certificates. The Shared Registration ...
... certificates issued
by a commercial certification authority for both registrar clients
and public registry RRP ...
... RRP server.
Initially, the server waits for a client connection and
authentication (PRE). All client ...
... | Waiting for |-------------------+
Authentication Succeeded | Client | |
+---------| Authentication | Authentication ...
...
If the authentication fails, the server gives the client another
chance to identify itself (WFR). If the authentication fails again,
...
... the server disconnects (DIS). Otherwise, the server waits for a
request from the client (WFC). Upon receiving a request, the server
executes it and responds to the client ...
... client (WFC). Upon receiving a request, the server
executes it and responds to the client with the result (EXE). The
server then waits again for another request from the client (WFC). If
...
... executes it and responds to the client with the result (EXE). The
server then waits again for another request from the client (WFC). If
the client sends a QUIT command ...
... server then waits again for another request from the client (WFC). If
the client sends a QUIT command, the server ends the session and
...
... DIS). To keep its state in sync with that of the server,
the client SHOULD wait for a response from the server before sending
another request on the same connection. The following table
...
... summarizes these states:
PRE Waiting for client connection and authentication
WFR Waiting for authentication ...
... authentication retry
WFC Waiting for a command from an authenticated client
EXE Executing a command
DIS ...
... period of 10 minutes SHOULD be used. The server MAY disconnect if the
server is in one of these states and no message is received from the
client during the timeout period.
...
... processing can be attempted.
421 Command failed due to server error. Client should try again A
transient server error has caused RRP command failure. A subsequent
...
...
500 Invalid command name
A client-specified RRP command name was not recognized as a valid RRP ...
...
501 Invalid command option
A client-specified RRP command parameter was not recognized as a
valid ...
... 503 Invalid attribute name
A client-specified RRP command parameter was not recognized as a
valid ...
... 504 Missing required attribute
A parameter required to execute the RRP command was not provided by
the client. The command should be retried with all required
parameters specified.
...
... A supplied parameter value is syntactically incorrect. For example, a
year value digit such as "5" may be required but the client provided
a string of characters such as "five".
...
... 506 Invalid option value
A client-specified value for an RRP command parameter is out-of-
bounds or otherwise not within acceptable System limits.
...
... entity
An entity required for command completion was not provided by the
client. For example, the CHECK command requires specification of
either a "Domain" entity ...
... A command parameter that isn't really optional (such as the registrar
ID in a SESSION command) was not provided by the client. The command
should be retried with all needed parameters.
...
... connection; <why>
A timeout event has been detected, and the client's session is being
ended. The System SHOULD define timeout periods to begin a client ...
... client's session is being
ended. The System SHOULD define timeout periods to begin a client
command, complete a client command, and for the duration of an open
...
... ended. The System SHOULD define timeout periods to begin a client
command, complete a client command, and for the duration of an open
session. The reason for the timeout MUST be provided at the end of
...
...
The session between the client and the server is intended to be an
alternating dialogue. Each command issued by a client MUST be acted
...
... session between the client and the server is intended to be an
alternating dialogue. Each command issued by a client MUST be acted
upon by the server, which MUST return a response code ...
... entity block elements.
Client-side implementers are strongly urged to observe the order of
command elements ...