RFC 3181: Signaled Preemption Priority Policy Element
In plain English — editorial summary, not part of the RFC
This document describes a preemption priority policy element for use by signaled policy based admission protocols (such as the Resource ReSerVation Protocol (RSVP) and Common Open Policy Service (COPS). [STANDARDS-TRACK]
Document record
- Document ID
- RFC3181
- Published
- October 2001
- Authors
- S. Herzog
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 12
- Also known as
- —
- Obsoletes:
- RFC 2751
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2749COPS usage for RSVPCurrent
January 2000
- RFC 3182Identity Representation for RSVPCurrent
October 2001
- RFC 2940Definitions of Managed Objects for Common Open Policy Service (COPS) Protocol ClientsCurrent
October 2000
- RFC 2872Application and Sub Application Identity Policy Element for Use with RSVPCurrent
June 2000
- RFC 2750RSVP Extensions for Policy ControlCurrent
January 2000
- RFC 2748The COPS (Common Open Policy Service) ProtocolUpdated
January 2000
- RFC 3175Aggregation of RSVP for IPv4 and IPv6 ReservationsUpdated
September 2001
- RFC 3209RSVP-TE: Extensions to RSVP for LSP TunnelsUpdated
December 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?