Resource ReSerVation Protocol API (RAPI)

Resource ReSerVation Protocol API (RAPI)
Copyright © 1998 The Open Group

RAPI Objects

Flowspecs, filter specs, sender templates, and sender Tspecs are encoded as variable-length RAPI objects.

Every RAPI object begins with a header of type rapi_hdr_t, which contains:

The total length of the object in bytes.
The type.

An empty object consists only of a header, with type zero and length sizeof (rapi_hdr_t).

Integrated services data structures are defined in referenced document RFC 2210, which describes the use of RSVP with the Controlled-Load and Guaranteed services. RSVP defines several data objects which carry resource reservation information but are opaque to RSVP itself. The usage and data format of those objects is given in the referenced document RFC 2210.

Flowspecs

There are two formats for RAPI flowspecs. For further details, see <rapi.h> in Header File .

RAPI_FLOWSTYPE_Simplified

This is a simplified format. It consists of a simple list of parameters needed for either Guaranteed or Controlled Load service, using the service type QOS_GUARANTEED or QOS_CNTR_LOAD, respectively.

The RAPI client library routines map this format to/from an appropriate Integrated Services data structure.

RAPI_FLOWSTYPE_Intserv

This flowspec must be a fully formatted Integrated Services flowspec data structure.

Upcalls

In an upcall, a flowspec is by default delivered in simplified format. However, if the RAPI_USE_INTSERV flag was set in the rapi_session() call, then the IntServ format is used in upcalls.

Sender Tspecs

There are two formats for RAPI Sender Tspecs. For further details, see <rapi.h> in Header File .

RAPI_TSPECTYPE_Simplified

This is a simplified format, consisting of a simple list of parameters with the service type QOS_TSPEC. The RAPI client library routines map this format to/from an appropriate Integrated Services data structure.

RAPI_TSPECTYPE_Intserv

This flowspec must be a fully formatted Integrated Services Tspec data structure.

Upcalls

In an upcall, a sender Tspec is by default delivered in simplified format. However, if the RAPI_USE_INTSERV flag was set in the rapi_session() call, then the IntServ format is used in upcalls.

Adspecs

There are two formats for RAPI Adspecs. For further details, see <rapi.h> in Header File .

RAPI_ADSTYPE_Simplified

This is a simplified format, consisting of a list of Adspec parameters for all possible services. The RAPI client library routines maps this format to/from an appropriate Integrated Services data structure.

RAPI_ADSTYPE_Intserv

This flowspec must be a fully formatted Integrated Services Tspec data structure.

Upcalls

In an upcall, an Adspec is by default delivered in simplified format. However, if the RAPI_USE_INTSERV flag was set in the rapi_session() call, then the IntServ format is used in upcalls.

Filter Specs and Sender Templates

There are two formats for these objects:

RAPI_FILTERFORM_BASE (RAPI_FILTERFORM_BASE6)
This object consists of only a socket address structure, defining the IPv4 address and port or, alternatively, the IPv6 address and flowlabel.
RAPI_FILTERFORM_GPI (RAPI_FILTERFORM_GPI6)
This object consists of only an address structure, defining the IP V4 (or V6) address and a 32-bit Generalized Port Identifier. It is recommended for all IPSEC applications.
Other non-TCP/non-UDP transports may also utilize this format in the future.

Policy Data Objects

Under RSVP, applications may need to supply policy information containing permission rights to obtain the preferential access to the network that they request. The rapi_policy_t type is a framework to carry the aforementioned integrity policy object.

Contents

Next section

Index