Transport Provider Interface (TPI), Version 2 Draft 2
Copyright © 1999 The Open Group

INDEX

[ 1 3 6 a c d e f g h i k m n o p q r s t u v w

[

Transport Service State Tables - [??]

1

Footnotes - 1.

3

The Common Single Type Model Implementation - 32-bit

6

Possible Multiple Type Model Implementation Methodologies - 64-bit

a

Connection Acceptance, Accepting Incoming Connections, Acknowledgements, Connection Acceptance - address, Allowable Sequence of TPI Primitives, Allowable Sequence of TPI Primitives - allowable sequence of TPI primitives, Intended Audience

c

Overview of Error Handling Capabilities, CLTS, The Common Single Type Model Implementation, Connection Acceptance, Connection Acceptance - connection acceptance, How TPI Works - connectionless-mode, Rules for Transport Service Interface Sequence of Primitives - connectionless-mode, Transport Service State Tables - connectionless mode, How TPI Works - connection-mode, Rules for Transport Service Interface Sequence of Primitives - connection-mode, Transport Service State Tables - connection-oriented mode, Accepting Incoming Connections, Typographical Conventions, Corrigenda, COTS

d

Transport Service State Tables - data transfer state table for CLTS, Transport Service State Tables - data transfer state table for COTS, This Document, Referenced Documents

e

Connection Acceptance - endpoint, Fatal Errors - EPROTO, Overview of Error Handling Capabilities, Non-fatal Errors, Fatal Errors, Allowable Sequence of TPI Primitives - event, Outgoing Events, Incoming Events

f

Fatal Errors, Fatal Errors - fatal error, Rules for Flushing Queues, Rules for Flushing Queues - flushing queues, TPI Message Formats, Optional TPI Message Formats, Frontmatter

g

Glossary, The Open Group, Open Group Publications

h

Overview of Error Handling Capabilities, How TPI Works

i

The Common Single Type Model Implementation, Possible Multiple Type Model Implementation Methodologies, DESCRIPTION - implementation-defined, Connection Acceptance - implementation-defined, STREAMS-based Transport Provider Interface - implementations, Incoming Events, Accepting Incoming Connections, Incoming Events - incoming events, Ordering Information, Transport Service State Tables - initialization state table, Intended Audience, STREAMS-based Transport Provider Interface, Rules for Transport Service Interface Sequence of Primitives, IP, How TPI Works - ISO IS 8072, How TPI Works - ISO IS 8072/DAD, Versions and Issues of Specifications

k

Incoming Events - kernel level incoming events, Outgoing Events - kernel level outgoing events, TPI States - kernel level states

m

Trade Marks, How TPI Works - M_DATA, How TPI Works - M_ERROR, Fatal Errors - M_ERROR, TPI Message Formats, Optional TPI Message Formats, TPI Message Formats - message format, Optional TPI Message Formats - message format, How TPI Works - message interface, Transport Primitives - message type, Possible Multiple Type Model Implementation Methodologies, How TPI Works - M_FLUSH, Rules for Flushing Queues - M_FLUSH, The Common Single Type Model Implementation, Possible Multiple Type Model Implementation Methodologies, Type Model, How TPI Works - M_PCPROTO, How TPI Works - M_PROTO, Possible Multiple Type Model Implementation Methodologies, Possible Multiple Type Model Implementation Methodologies - multiple, type

n

Non-fatal Errors, Non-fatal Errors - non-fatal error

o

The Open Group, Open Group Publications, Optional TPI Message Formats, Optional TPI Message Formats - optional TPI message formats, Ordering Information, STREAMS-based Transport Provider Interface - OSI, Outgoing Events, Outgoing Events - outgoing events, Overview of Error Handling Capabilities

p

Possible Multiple Type Model Implementation Methodologies, Rules for Precedence of TPI Primitives on a Stream, Rules for Precedence of TPI Primitives on a Stream - precedence rules, Preface, How TPI Works - primitive, Rules for Transport Service Interface Sequence of Primitives - primitive, Allowable Sequence of TPI Primitives - primitive, Rules for Transport Service Interface Sequence of Primitives, Rules for Precedence of TPI Primitives on a Stream, Receipt of Unknown Primitives, Transport Primitives, Allowable Sequence of TPI Primitives, Transport Primitives - primitives list, STREAMS-based Transport Provider Interface - protocol, STREAMS-based Transport Provider Interface, Connection Acceptance - provider, Open Group Publications

q

Rules for Flushing Queues

r

Receipt of Unknown Primitives, Referenced Documents, Rules for Transport Service Interface Sequence of Primitives, Rules for Precedence of TPI Primitives on a Stream, Rules for Flushing Queues, Rules for Flushing Queues - rules for flushing queues, Rules for Precedence of TPI Primitives on a Stream - rules for precedence, Rules for Transport Service Interface Sequence of Primitives - rules for TPI sequence of primitives

s

Rules for Transport Service Interface Sequence of Primitives, Allowable Sequence of TPI Primitives, Rules for Transport Service Interface Sequence of Primitives - sequence of primitives, Rules for Transport Service Interface Sequence of Primitives, Transport Service State Tables, The Common Single Type Model Implementation, The Common Single Type Model Implementation - single type model, Versions and Issues of Specifications, Transport Service State Tables, Allowable Sequence of TPI Primitives - state, TPI States, TPI States - state table, Transport Service State Tables - state table, Transport Service State Tables - state table, data transfer for CLTS, Transport Service State Tables - state table, data transfer for COTS, Transport Service State Tables - state table, initialization, Variables - state table variables, Rules for Precedence of TPI Primitives on a Stream, STREAMS-based Transport Provider Interface - streams, How TPI Works - streams, STREAMS, STREAMS-based Transport Provider Interface, How TPI Works - streams message, Transport Primitives - streams message type, Structure

t

Transport Service State Tables, T_ADDR_ACK, T_ADDR_REQ, T_BIND_ACK, T_BIND_REQ, T_CAPABILITY_ACK, T_CAPABILITY_REQ, T_CONN_CON, T_CONN_IND, T_CONN_REQ, T_CONN_RES, TCP, T_DATA_IND, T_DATA_REQ, T_DISCON_IND, T_DISCON_REQ, T_ERROR_ACK, T_EXDATA_IND, T_EXDATA_REQ, This Document, T_INFO_ACK, T_INFO_REQ, T_OK_ACK, T_OPTDATA_IND, T_OPTDATA_REQ, T_OPTMGMT_ACK, T_OPTMGMT_REQ, T_ORDREL_IND, T_ORDREL_REQ, How TPI Works, Rules for Precedence of TPI Primitives on a Stream, TPI States, Allowable Sequence of TPI Primitives, TPI Message Formats, Optional TPI Message Formats, TPI, TPI Message Formats - TPI message formats, Trade Marks, STREAMS-based Transport Provider Interface, Rules for Transport Service Interface Sequence of Primitives, Transport Primitives, Transport Service State Tables, Connection Acceptance - transport address, Connection Acceptance - transport endpoint, ., STREAMS-based Transport Provider Interface - transport layer, How TPI Works - transport primitive, Transport Primitives - transport primitives, How TPI Works - transport provider, Connection Acceptance - transport provider, How TPI Works - transport service definitions, Transport Service State Tables - transport service state table, Allowable Sequence of TPI Primitives - transport user, Connection Acceptance - transport user, T_UDERROR_IND, T_UNBIND_REQ, T_UNITDATA_IND, T_UNITDATA_REQ, The Common Single Type Model Implementation, Possible Multiple Type Model Implementation Methodologies, Type Model, Typographical Conventions

u

UI, Receipt of Unknown Primitives, Receipt of Unknown Primitives - unknown primitives, Connection Acceptance - user, USL

v

Variables - variables, Variables, Versions and Issues of Specifications

w

How TPI Works