RFC 2380: RSVP over ATM Implementation Requirements
In plain English — editorial summary, not part of the RFC
This memo presents specific implementation requirements for running RSVP over ATM switched virtual circuits (SVCs). It presents requirements that ensure interoperability between multiple implementations and conformance to the RSVP and Integrated Services specifications. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2380
- Published
- August 1998
- Authors
- L. Berger
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3175Aggregation of RSVP for IPv4 and IPv6 ReservationsUpdated
September 2001
- RFC 3936Procedures for Modifying the Resource reSerVation Protocol (RSVP)Current
October 2004
- RFC 2381Interoperation of Controlled-Load Service and Guaranteed Service with ATMCurrent
August 1998
- RFC 2379RSVP over ATM Implementation GuidelinesCurrent
August 1998
- RFC 2745RSVP Diagnostic MessagesCurrent
January 2000
- RFC 2746RSVP Operation Over IP TunnelsCurrent
January 2000
- RFC 2747RSVP Cryptographic AuthenticationUpdated
January 2000
- RFC 2814SBM (Subnet Bandwidth Manager): A Protocol for RSVP-based Admission Control over IEEE 802-style networksCurrent
May 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?