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


Technical Standard
Resource ReSerVation Protocol API (RAPI)
Document Number: C809
ISBN: 1-85912-226-4

©December 1998, The Open Group All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of the copyright owners.

Any comments relating to the material contained in this document may be submitted to The Open Group at:

The Open Group
Apex Plaza
Forbury Road
Berkshire, RG1 1AX
United Kingdom
or by electronic mail to:


The Open Group

The Open Group is the leading vendor-neutral, international consortium for buyers and suppliers of technology. Its mission is to cause the development of a viable global information infrastructure that is ubiquitous, trusted, reliable, and as easy-to-use as the telephone. The essential functionality embedded in this infrastructure is what we term the IT DialTone. The Open Group creates an environment where all elements involved in technology development can cooperate to deliver less costly and more flexible IT solutions.

Formed in 1996 by the merger of the X/Open Company Ltd. (founded in 1984) and the Open Software Foundation (founded in 1988), The Open Group is supported by most of the world's largest user organizations, information systems vendors, and software suppliers. By combining the strengths of open systems specifications and a proven branding scheme with collaborative technology development and advanced research, The Open Group is well positioned to meet its new mission, as well as to assist user organizations, vendors, and suppliers in the development and implementation of products supporting the adoption and proliferation of systems which conform to standard specifications.

With more than 200 member companies, The Open Group helps the IT industry to advance technologically while managing the change caused by innovation. It does this by:

The Open Group operates in all phases of the open systems technology lifecycle including innovation, market adoption, product development, and proliferation. Presently, it focuses on seven strategic areas: open systems application platform development, architecture, distributed systems management, interoperability, distributed computing environment, security, and the information superhighway. The Open Group is also responsible for the management of the UNIX trademark on behalf of the industry.

Development of Product Standards

This process includes the identification of requirements for open systems and, now, the IT DialTone, development of Technical Standards (formerly CAE and Preliminary Specifications) through an industry consensus review and adoption procedure (in parallel with formal standards work), and the development of tests and conformance criteria.

This leads to the preparation of a Product Standard which is the name used for the documentation that records the conformance requirements (and other information) to which a vendor may register a product.

The "X" Device is used by vendors to demonstrate that their products conform to the relevant Product Standard. By use of the Open Brand they guarantee, through the Open Brand Trade Mark License Agreement (TMLA), to maintain their products in conformance with the Product Standard so that the product works, will continue to work, and that any problems will be fixed by the vendor.

Open Group Publications

The Open Group publishes a wide range of technical documentation, the main part of which is focused on development of Technical Standards and product documentation, but which also includes Guides, Snapshots, Technical Studies, Branding and Testing documentation, industry surveys, and business titles.

There are several types of specification:

In addition, The Open Group publishes:

Versions and Issues of Specifications

As with all live documents, Technical Standards and Specifications require revision to align with new developments and associated international standards. To distinguish between revised specifications which are fully backwards compatible and those which are not:


Readers should note that Corrigenda may apply to any publication. Corrigenda information is published on the World-Wide Web at

Ordering Information

Full catalogue and ordering information on all Open Group publications is available on the World-Wide Web at

This Document
This Technical Standard is based on the Internet Engineering Task force (IETF) Internet Draft version 5 for RAPI, which is a specific Application Programming Interface (API) for the Resource ReSerVation Protocol (RSVP). Rather than develop this into an IETF RFC document, the IETF have deferred to The Open Group to develop RAPI into an open systems standard.

The RAPI interface is one realization of the generic API contained in the RSVP Functional Specification (see referenced document RFC 2205).

Intended Audience
This specification is intended for programmers who wish to implement RAPI, and those who wish to write applications to use it.

A Glossary and Index are also provided.

Typographical Conventions
The following typographical conventions are used throughout this document:


Motif®, OSF/1®, UNIX®, and the "X Device"® are registered trademarks and IT DialToneTM; and The Open GroupTM; are trademarks of The Open Group in the U.S. and other countries.


The Open Group gratefully acknowledges the permission of the authors-R.Braden (ISI) and D.Hoffman (Sun Microsystems)-of the IETF Internet Draft for RAPI (An RSVP Application Programming Interface, Version 5, June 16, 1997), for their approval to use their draft as the basis for this RAPI Technical Standard.

Referenced Documents

The following documents are referenced in this Technical Standard:

RFC 791

Internet Protocol, J. Postel, September 1981. Status: Standard.

RFC 1700

Assigned Numbers, J Reynolds, J. Postel, October 1994. Status: Standard.

RFC 2205

Resource ReSerVation Protocol (RSVP) - Version 1 Functional Specification, R. Braden, L. Zhang, S. Berson, September 1997. Status: Proposed Standard.

RFC 2210

The Use of RSVP with IETF Integrated Services, J. Wroclawski, September 1997. Status: Proposed Standard.

RFC 2211

Specification of the Controlled-Load Network Element Service, J. Wroclawski. September 1997. Status: Proposed Standard.

RFC 2212

Specification of Guaranteed Quality of Service, S. Shenker, C. Partridge, R. Guerin, September 1997. Status: Proposed Standard.

RFC 2215

General Characterization Parameters for Integrated Service Network Elements, S. Shenker, J. Wroclawski, September 1997. Status: Proposed Standard.

XNS, Issue 5

CAE Specification, February 1997, Networking Services, Issue 5 (ISBN: 1-85912-165-9, C523), published by The Open Group.

XSH, Issue 5

CAE Specification, January 1997, System Interfaces and Headers, Issue 5 (ISBN: 1-85912-181-0, C606), published by The Open Group.

The following referenced documents are not necessary for implementation of the specification, but provide additional information likely to be of value to implementors or application writers:

RFC 1825

Security Architecture for the Internet Protocol, commonly known as IPSEC, R. Atkinson, August 1995. Status: Proposed Standard.

RFC 1826

Internet Protocol Authentication Header, R. Atkinson, August 1995. Status: Draft Standard.

RFC 1827

Internet Protocol Encapsulating Security Payload (ESP), R. Atkinson, August 1995. Status: Draft Standard.

RFC 2207

RSVP Extensions for IPSEC Data Flows, L. Berger, T. O'Malley, September 1997.

RFC 2208

Resource ReSerVation Protocol (RSVP) - Version 1 Applicability Statement: Some Guidelines on Deployment, A. Mankin, Ed., F. Baker, B. Braden, S. Bradner, M. O`Dell, A. Romanow, A. Weinrib, L. Zhang, September 1997. Status: Informational.

RFC 2209

Resource ReSerVation Protocol (RSVP) - Version 1: Message Processing Rules, R. Braden, L. Zhang, September 1997. Status: Informational.

RFC 2216

Network Element Service Specification Template, S. Shenker, J. Wroclawski, September 1997. Status: Informational.

Contents Next section Index