RFC 3670: Information Model for Describing Network Device QoS Datapath Mechanisms
In plain English — editorial summary, not part of the RFC
The purpose of this document is to define an information model to describe the quality of service (QoS) mechanisms inherent in different network devices, including hosts. Broadly speaking, these mechanisms describe the properties common to selecting and conditioning traffic through the forwarding path (datapath) of a network device. This selection and conditioning of traffic in the datapath spans both major QoS architectures: Differentiated Services and Integrated Services. This document should be used with the QoS Policy Information Model (QPIM) to model how policies can be defined to manage and configure the QoS mechanisms (i.e., the classification, marking, metering, dropping, queuing, and scheduling functionality) of devices. Together, these two documents describe how to write QoS policy rules to configure and manage the QoS mechanisms present in the datapaths of devices. This document, as well as QPIM, are information models. That is, they represent information independent of a binding to a specific type of repository
Document record
- Document ID
- RFC3670
- Published
- January 2004
- Authors
- B. Moore; D. Durham; J. Strassner; A. Westerinen; W. Weiss
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 97
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3644Policy Quality of Service (QoS) Information ModelCurrent
November 2003
- RFC 3521Framework for Session Set-up with Media AuthorizationCurrent
April 2003
- RFC 2748The COPS (Common Open Policy Service) ProtocolUpdated
January 2000
- RFC 4710Real-time Application Quality-of-Service Monitoring (RAQMON) FrameworkCurrent
October 2006
- RFC 3374Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access NetworkCurrent
September 2002
- RFC 3313Private Session Initiation Protocol (SIP) Extensions for Media AuthorizationCurrent
January 2003
- RFC 3312Integration of Resource Management and Session Initiation Protocol (SIP)Updated
October 2002
- RFC 4032Update to the Session Initiation Protocol (SIP) Preconditions FrameworkCurrent
March 2005
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?