RFC 3086: Definition of Differentiated Services Per Domain Behaviors and Rules for their Specification
In plain English — editorial summary, not part of the RFC
This document defines and discusses Per-Domain Behaviors in detail and lays out the format and required content for contributions to the Diffserv WG on PDBs and the procedure that will be applied for individual PDB specifications to advance as WG products. This format is specified to expedite working group review of PDB submissions. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3086
- Published
- April 2001
- Authors
- K. Nichols; B. Carpenter
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8325Mapping Diffserv to IEEE 802.11Updated
February 2018
- RFC 2998A Framework for Integrated Services Operation over Diffserv NetworksCurrent
November 2000
- RFC 2997Specification of the Null Service TypeCurrent
November 2000
- RFC 2996Format of the RSVP DCLASS ObjectCurrent
November 2000
- RFC 3374Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access NetworkCurrent
September 2002
- RFC 2215General Characterization Parameters for Integrated Service Network ElementsCurrent
September 1997
- RFC 2212Specification of Guaranteed Quality of ServiceCurrent
September 1997
- RFC 4094Analysis of Existing Quality-of-Service Signaling ProtocolsCurrent
May 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?