RFC 2380 (rfc2380) - Page 2 of 14

RSVP over ATM Implementation Requirements

Alternative Format: Original Text Document
< Previous
Next >
RFC 2380       RSVP over ATM Implementation Requirements     August 1998


   4. Security Considerations ...................................... 11
   5. Acknowledgments .............................................. 11
   6. Author's Address ............................................. 12
   REFERENCES ...................................................... 13
   FULL COPYRIGHT STATEMENT ........................................ 14

1. Introduction

   This memo discusses running IP over ATM in an environment where SVCs
   are used to support QoS flows and RSVP is used as the internet level
   QoS signaling protocol.  It applies when using CLIP/ION, LANE2.0 and
   MPOA [4] methods for supporting IP over ATM.  The general issues
   related to running RSVP [8] over ATM have been covered in several
   papers including [9] and other earlier work.  This document is
   intended as a companion to [9,5].  The reader should be familiar with
   both documents.

   This document defines the specific requirements for implementations
   using ATM UNI3.x and 4.0.  These requirements must be adhered to by
   all RSVP over ATM implementations to ensure interoperability.
   Further recommendations to guide implementers of RSVP over ATM are
   provided in [5].

   The rest of this section will define terms and assumptions. Section 2
   will cover implementation guidelines common to all RSVP session.
   Section 3 will cover implementation guidelines specific to multicast
   sessions.

1.1 Terms

   The terms "reservation" and "flow" are used in many contexts, often
   with different meaning.  These terms are used in this document with
   the following meaning:

   o    Reservation is used in this document to refer to an RSVP
        initiated request for resources.  RSVP initiates requests for
        resources based on RESV message processing.  RESV messages that
        simply refresh state do not trigger resource requests.  Resource
        requests may be made based on RSVP sessions and RSVP reservation
        styles. RSVP styles dictate whether the reserved resources are
        used by one sender or shared by multiple senders.  See [8] for
        details of each. Each new request is referred to in this
        document as an RSVP reservation, or simply reservation.








Berger                      Standards Track
< Previous
Next >