RFC 2990: Next Steps for the IP QoS Architecture
In plain English — editorial summary, not part of the RFC
This document highlights the outstanding architectural issues relating to the deployment and use of QoS mechanisms within internet networks, noting those areas where further standards work may assist with the deployment of QoS internets. This document is the outcome of a collaborative exercise on the part of the Internet Architecture Board. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2990
- Published
- November 2000
- Authors
- G. Huston
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2884Performance Evaluation of Explicit Congestion Notification (ECN) in IP NetworksCurrent
July 2000
- RFC 2101IPv4 Address Behaviour TodayCurrent
February 1997
- RFC 2983Differentiated Services and TunnelsCurrent
October 2000
- RFC 2998A Framework for Integrated Services Operation over Diffserv NetworksCurrent
November 2000
- RFC 2977Mobile IP Authentication, Authorization, and Accounting RequirementsCurrent
October 2000
- RFC 3012Mobile IPv4 Challenge/Response ExtensionsObsoleted
November 2000
- RFC 2966Domain-wide Prefix Distribution with Two-Level IS-ISObsoleted
October 2000
- RFC 3022Traditional IP Network Address Translator (Traditional NAT)Current
January 2001
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?