RFC 2379: RSVP over ATM Implementation Guidelines
In plain English — editorial summary, not part of the RFC
This memo presents specific implementation guidelines for running RSVP over ATM switched virtual circuits (SVCs). This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC2379
- Published
- August 1998
- Authors
- L. Berger
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- tsv
- Pages
- 8
- Also known as
- BCP24
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2383ST2+ over ATM Protocol Specification - UNI 3.1 VersionCurrent
August 1998
- RFC 2269Using the MARS Model in non-ATM NBMA NetworksCurrent
January 1998
- RFC 2226IP Broadcast over ATM NetworksCurrent
October 1997
- RFC 2225Classical IP and ARP over ATMUpdated
April 1998
- RFC 2121Issues affecting MARS Cluster SizeCurrent
March 1997
- RFC 3210Applicability Statement for Extensions to RSVP for LSP-TunnelsCurrent
December 2001
- RFC 2366Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM NetworksObsoleted
July 1998
- RFC 2296HTTP Remote Variant Selection Algorithm -- RVSA/1.0Current
March 1998
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?