RFC 2751: Signaled Preemption Priority Policy Element
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3181.
Current version: 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 RSVP and COPS). [STANDARDS-TRACK]
Document record
- Document ID
- RFC2751
- Published
- January 2000
- Authors
- S. Herzog
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 12
- Also known as
- —
- Obsoleted by:
- RFC 3181
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2430A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE)Current
October 1998
- RFC 3216SMIng ObjectivesCurrent
December 2001
- RFC 2752Identity Representation for RSVPObsoleted
January 2000
- RFC 2379RSVP over ATM Implementation GuidelinesCurrent
August 1998
- RFC 3210Applicability Statement for Extensions to RSVP for LSP-TunnelsCurrent
December 2001
- RFC 2749COPS usage for RSVPCurrent
January 2000
- RFC 2490A Simulation Model for IP Multicast with RSVPCurrent
January 1999
- RFC 6076Basic Telephony SIP End-to-End Performance MetricsCurrent
January 2011
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?