Export (0) Print
Expand All

1.1 Glossary

The following terms are defined in [MS-GLOS]:

Augmented Backus-Naur Form (ABNF)
base64
binary large object (BLOB)
certificate
client
dynamic endpoint
endpoint
globally unique identifier (GUID)
HTTP client
HTTP proxy
HTTP server
inbound
Internet host name
little-endian
outbound
PDU stream
protocol data unit (PDU)
protocol dialect
proxy
receive window
remote procedure call (RPC)
RPC client
RPC PDU
RPC protocol sequence
RPC server
RPC transport
server
universally unique identifier (UUID)
URI
well-known endpoint

The following terms are specific to this document:

channel lifetime: The maximum content length of an IN channel or OUT channel (in bytes).

channel recycling: The set of mechanisms involved in closing an open IN or OUT channel N and opening a new IN or OUT channel N+1. The opening and subsequent closing occur as part of the sequence of channels forming a virtual IN or OUT channel.

echo request: A message sent to an inbound proxy or outbound proxy in order to elicit a response.

echo response: A message sent by an inbound proxy or outbound proxy in response to an echo request.

expired: A state of IN channel or OUT channel in which the maximum content length has been reached or exceeded and it can no longer accept any PDU awaiting transmission. See also channel lifetime. For more details, see section 2.1.2.1.7.

IN channel: An inbound HTTP request or an inbound TCP/IP connection between two network nodes acting in one of the roles defined by this protocol. An IN channel is independent from the underlying transport and can be based on an HTTP or HTTPS request or on a TCP connection.

IN channel recycling: The set of mechanisms involved in closing an open IN channel N and opening a new IN channel N+1. The opening and subsequent closing occur as part of the sequence of channels forming a virtual IN channel.

inbound proxy: A network node that acts as an RPC over HTTP proxy for inbound traffic between an RPC client and an RPC server.

mixed proxy: A network node that acts as a proxy for both inbound and outbound traffic between a client and a server.

OUT channel: An outbound HTTP response or an outbound TCP/IP connection between two network nodes acting in one of the roles defined by a protocol. An OUT channel is independent from the underlying transport and can be based on an HTTP or HTTPS response or on a TCP connection.

OUT channel recycling: The set of mechanisms involved in closing an open OUT channel N and opening a new OUT channel N+1. The opening and subsequent closing occur as part of the sequence of channels forming a virtual OUT channel.

outbound proxy: A network node that acts as an RPC over HTTP proxy for outbound traffic between an RPC client and an RPC server.

plug a channel: The act of switching a channel from unplugged channel mode to plugged channel mode.

plugged channel mode: A channel mode in which an IN channel or OUT channel instance queues protocol data units (PDUs) instead of sending them immediately.

predecessor channel: In the context of IN channel recycling or OUT channel recycling, the previous IN channel or OUT channel (–1 where N is the reference point) in the sequence of channels forming a virtual IN channel or virtual OUT channel.

predecessor inbound proxy: An inbound proxy to which a predecessor channel was established.

predecessor outbound proxy: An outbound proxy to which a predecessor channel was established.

replacement channel: An IN channel or OUT channel other than the first in the sequence of IN channels or OUT channels that constitute a virtual IN channel or virtual OUT channel.

Request to Send (RTS) cookie: A 16-byte cryptographically strong random number exchanged between parties in a remote procedure call (RPC) over HTTP protocol sequence. An RTS cookie has the same uniqueness requirements as a UUID, and implementations can use a UUID as the RTS cookie. An RTS cookie is used to reference virtual connections, IN channels, OUT channels, and other protocol entities.

Request to Send (RTS) Protocol Data Unit (PDU): A PDU that is used to control communication settings on an IN channel or OUT channel, virtual IN channel or virtual OUT channel, or virtual connection.

RPC over HTTP proxy: A mixed proxy, inbound proxy, or outbound proxy.

successor channel: In the context of IN channel recycling or OUT channel recycling, the next IN channel or OUT channel in the sequence of channels forming a virtual IN channel or virtual OUT channel (N+1 where N represents the reference point in the sequence).

successor inbound proxy: An inbound proxy to which a successor channel is established.

successor outbound proxy: An outbound proxy to which a successor channel is established.

unplug a channel: To switch a channel from plugged channel mode to unplugged channel mode.

unplugged channel mode: A channel mode in which an IN channel or OUT channel instance sends protocol data units (PDUs) immediately instead of queuing them. This is the default mode for channels.

virtual connection: A pair consisting of one virtual IN channel and one virtual OUT channel between the same remote procedure call (RPC) client and RPC server that provides full-duplex, reliable, in-order, at-most-once delivery communication capabilities.

virtual IN channel: A communication session between a remote procedure call (RPC) client and an RPC server that can span multiple IN channels. When the communication session spans multiple IN channels, the IN channels are sequentially ordered in time with partial overlap in time between channel N and channel N+1 in the sequence. A virtual IN channel provides half-duplex, RPC client-to-RPC server, reliable, in-order, at-most-once delivery communication capabilities.

virtual OUT channel: A communication session between a remote procedure call (RPC) client and an RPC server that can span multiple OUT channels. When the communication session spans multiple OUT channels, the OUT channels are sequentially ordered in time with partial overlap in time between channel N and channel N+1 in the sequence. A virtual OUT channel provides half-duplex, RPC server-to-RPC client, reliable, in-order, at-most-once delivery communication capabilities.

MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as described in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.

 
Show:
© 2015 Microsoft