1 - 2 - 3 - 4 - 6 - 8 - A - B - C - D - E - F - G - H - I - J - K - L - M - N - O - P - Q - R - S - T - U - V - W - X
version
Click on the red underlined text to get to the source
... packet is entirely
encrypted except for the Client, Version, Domain, Length and Packet
Flags fields at the beginning of the packet. Client identifiers ...
... Nelson's [2] remote procedure call mechanism. An earlier version of the
protocol was described in SIGCOMM'86 [6]. The rate-based flow ...
... 8] described in RFC 966(-> 988(-> 1112std5 | 1054(-> 1112std5)))
and 988. The secure version of the protocol is similar to that
described by Birrell [1] for secure RPC ...
... Version The 3-bit identifier specifying the version of the
protocol. Current version is version ...
... not detect the erroneous swapping of 16-bit words, which may easily
occur due to software errors. A future version of VMTP is expected to
include a more secure algorithm ...
... described in Section 3.2 with the following qualifications.
Client, Version, Domain, Transaction
...
... the Response stored there as well as those queued. In
addition, GetResponse must create a queued version of this
Response before allowing it to be overwritten.
...
... 2. The procedure HandleRequestNoCSR is specified in Section
5.8.1. In the minimal client version, it need only handle
Probe requests and can do so directly without allocating a
...
... The CSR for a server is extended with the following fields, in addition
to the ones listed for the client version.
RemoteClient Identifier ...
... +-------------+----------------+-------------------+
| ControlFlags| Interface | Version/Procedure |
+-------------+----------------+-------------------+
8 bits ...
... An interface is free to allocate the 8 bits for version and procedure as
desired. For example, all 8 bits can be used for procedures. A module
...
... desired. For example, all 8 bits can be used for procedures. A module
requiring more than 256 Version/Procedure values can be allocated
multiple Interface ...
... out unless the request is a datagram request. (Non-blocking versions
with signals on completion could also be provided, especially with a
streaming implementation.)
...