RFC 2386: A Framework for QoS-based Routing in the Internet
In plain English — editorial summary, not part of the RFC
This document describes some of the QoS-based routing issues and requirements, and proposes a framework for QoS-based routing in the Internet. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2386
- Published
- August 1998
- Authors
- E. Crawley; R. Nair; B. Rajagopalan; H. Sandick
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8815Deprecating Any-Source Multicast (ASM) for Interdomain MulticastCurrent
August 2020
- RFC 2676QoS Routing Mechanisms and OSPF ExtensionsCurrent
August 1999
- RFC 2215General Characterization Parameters for Integrated Service Network ElementsCurrent
September 1997
- RFC 2212Specification of Guaranteed Quality of ServiceCurrent
September 1997
- RFC 2748The COPS (Common Open Policy Service) ProtocolUpdated
January 2000
- RFC 2996Format of the RSVP DCLASS ObjectCurrent
November 2000
- RFC 2997Specification of the Null Service TypeCurrent
November 2000
- RFC 2998A Framework for Integrated Services Operation over Diffserv NetworksCurrent
November 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?