Skip to main content

Signaled Preemption Priority Policy Element

The information below is for an old version of the document that is already published as an RFC.
Document Type This is an older version of an Internet-Draft that was ultimately published as an RFC.
Author Shai Herzog
Last updated 2013-03-02 (Latest revision 2001-05-22)
Stream Internet Engineering Task Force (IETF)
Stream WG state (None)
Document shepherd (None)
IESG IESG state RFC 3181 (Proposed Standard)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3181

        Title:      Signaled Preemption Priority Policy Element
        Author(s):  S. Herzog
        Status:     Standards Track
        Date:       October 2001
        Pages:      12
        Characters: 21990
        Obsoletes:  RFC 2751

        I-D Tag:    draft-ietf-rap-signaled-priority-v2-01.txt


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).

Preemption priority defines a relative importance (rank) within the
set of flows competing to be admitted into the network. Rather than
admitting flows by order of arrival (First Come First Admitted)
network nodes may consider priorities to preempt some previously
admitted low priority flows in order to make room for a newer,
high-priority flow.

This memo corrects an RSVP POLICY_DATA P-Type codepoint assignment
error in RFC 2751.

This document is a product of the Resource Allocation Protocol Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.