ANSI INCITS-337-2000 pdf download Information Technology – Scheduled Transfer Protocol (ST)
3.1.22 Opaque data: Four bytes of Source ULP to Destination ULP peer-to-peer information carried in a Data operation’s Schedule Header sepa- rately from the data payload. (See 6.2.14, page 32) 3.1.23 operation: The procedure defined by the parameters in a Schedule Header, and any payload associated with that Schedule Header (see figure 2, page 5). The code in the Schedule Header’s “Op” field identifies the operation’s name/function (see table 2, page 36).
3.1.24 optional: Characteristics that are not required by ST. However, if any optional characteristic is implemented, it shall be implemented as defined in ST.
3.1.25 persistent: Memory that is maintained for multiple Put, Get, and FetchOp operations. (See 6.1.4, page 21.)
3.1.26 Port or ST-Port: A logical connection within an end device. When the possibility of con- fusion exists with ULP-Ports the term ST-Port may be used; otherwise the shorter term Port is used. (See 5.2.1, page 11.)
3.1.27 Put: An operation to write data into a per- sistent memory region on a remote end device. (See 6.1.4.2, page 23.) 3.1.28 Request For Comment (RFC): RFC (Request For Comment) documents are working standards documents from the TCP/IP internet- working community. Copies of these documents are available from numerous electronic sources (e.g., http://www.ietf.org) or by writing to Internet Engineering Task Force (IETF) Secretariat, c/o Corporation for National Research Initiatives, 1895 Preston White Drive, Suite 100 Reston, VA 20191-5434, USA.
3.1.29 Responder: The end device that responds to the sequence of operations started by the Initiator. This is typically a host computer sys- tem, but may also be a non-transparent translator, bridge, or router.
3.1.30 Schedule Header queue: An ordered list of entities, referred to as Slots, containing Sched- ule Headers (see figure 4, page 5).
3.1.31 Scheduled Transfer: An information transfer, normally used for bulk data movement, where the end devices prearrange the transfer using the protocol defined in this standard.
3.1.32 Scheduled Transfer Unit (STU): The data payload portion of a Data operation. STUs are the basic components of Blocks and are the smallest units transferred. (See figure 3, page 6, and 6.2.8, page 30.)
3.1.33 segment: That portion of a Block covered by a single checksum (see 8.3.2, page 38). A segment contains one or more STUs.
3.1.34 sequence: An ordered group of operations providing a particular function, e.g., Read, Write, Get, etc., between an Initiator and a Responder. The roles of Initiator and Responder are constant for all operations in the sequence.
3.1.35 Slot: A space in the end device reserved for a Control operation, or the Schedule Header portion of a Data operation. (See 5.2.5, page 12.)
3.1.36 Source: The end device that sends an operation or data. 3.1.37 ST Buffer Size: The unit of memory ad- dressed by ST for Bufx and Offset calculations (see 6.2.9, page 30) and expressed as 2 Bufsize bytes (see 5.2.3, page 12).