Lines Matching full:protocol
10 .OH 'Remote Procedure Calls: Protocol Specification''Page %'
11 .EH 'Page %''Remote Procedure Calls: Protocol Specification'
14 \&Remote Procedure Calls: Protocol Specification
19 Note: This chapter specifies a protocol that Sun Microsystems, Inc.,
27 This chapter specifies a message protocol used in implementing
28 Sun's Remote Procedure Call (RPC) package. (The message protocol is
31 .I "External Data Representation Standard: Protocol Specification"
44 documented in the specific program's protocol specification (see the
45 \fIPort Mapper Program Protocol\fP\, below, for an example). Network
84 The RPC protocol makes no restrictions on the concurrency model
94 The RPC protocol is independent of transport protocols. That is, RPC
96 The protocol deals only with specification and interpretation of
101 type of transport protocol underneath RPC. If it knows it is running
108 Because of transport independence, the RPC protocol does not attach
111 by) the underlying transport protocol. For example, consider RPC
135 connection-oriented protocol like TCP is used, an application still
139 connection-oriented protocols. For example, a request-reply protocol
152 itself\(emsee the \fIPort Mapper Program Protocol\fP\, below).
154 Implementors should think of the RPC protocol as the jump-subroutine
162 The RPC protocol provides the fields necessary for a client to
166 in the RPC header indicates which protocol is being used. More
172 \&RPC Protocol Requirements
174 The RPC protocol must provide for the following:
184 worth supporting because of protocol roll-over errors, implementation
187 RPC protocol mismatches.
189 Remote program protocol version mismatches.
191 Protocol errors (such as misspecification of a procedure's parameters).
207 identifies which version of the protocol the caller is using.
212 numbers are documented in the specific program's protocol
213 specification. For example, a file service's protocol specification
218 the actual RPC message protocol could also change. Therefore, the
225 The remote implementation of RPC does speak protocol version 2.
235 caller side protocol or programming error.)
239 disagreement about the protocol between client and service.)
244 provided as a part of the RPC protocol. The call message has two
247 protocol specification defines all three fields to be the following
270 enumeration followed by bytes which are opaque to the RPC protocol
275 authentication protocol specifications. (See
313 \&Other Uses of the RPC Protocol
315 The intended use of this protocol is for calling remote procedures.
317 However, the protocol itself is a message-passing protocol with which
319 perhaps abuses, the RPC message protocol for the following two
341 its semantics. See the \fIPort Mapper Program Protocol\fP\, below,
345 \&The RPC Message Protocol
347 This section defines the RPC message protocol in the XDR data
439 * In version 2 of the RPC protocol specification, rpcvers must
447 * protocol.
484 * accept_stat. The \fISUCCESS\fP arm of the union is protocol
520 * protocol (\fIRPC_MISMATCH\fP), or the server refuses to
541 open-ended to the rest of the RPC protocol. This section defines
747 \&DES Authentication Protocol (in XDR language)
868 authentication protocol are:
939 in the protocol. Rather, it is used only to encrypt a conversation
956 When RPC messages are passed on top of a byte stream protocol (like
959 user protocol errors. This is called record marking (RM). Sun uses
1038 again. By convention, procedure 0 of any RPC protocol should have
1044 is the original version of the protocol
1049 matures it may be dropped from the protocol entirely.
1097 \&Port Mapper Program Protocol
1119 \&Port Mapper Protocol Specification (in RPC Language)
1128 * A mapping of (program, version, protocol) to port number
1143 const IPPROTO_TCP = 6; /* \fIprotocol number for TCP/IP \fP*/
1144 const IPPROTO_UDP = 17; /* \fIprotocol number for UDP/IP \fP*/
1224 protocol takes no parameters and returns no results.
1229 protocol number "prot", and the port "port" on which it awaits
1242 The protocol and port number fields of the argument are ignored.
1245 protocol number "prot", this procedure returns the port number on
1252 version, protocol, and port values.
1281 [2] Cheriton, D.; "VMTP: Versatile Message Transaction Protocol",
1293 [6] Postel, J.; "Transmission Control Protocol - DARPA Internet
1294 Program Protocol Specification", RFC 793; Information Sciences
1297 [7] Postel, J.; "User Datagram Protocol", RFC 768; Information Sciences