RFC 3181 on Signaled Preemption Priority Policy Element
RFC Editor <rfc-ed@ISI.EDU> Fri, 02 November 2001 01:02 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04488; Thu, 1 Nov 2001 20:02:08 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA01596 for ietf-123-outbound.10@ietf.org; Thu, 1 Nov 2001 19:55:01 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA01478 for <all-ietf@loki.ietf.org>; Thu, 1 Nov 2001 19:41:15 -0500 (EST)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04083 for <all-ietf@ietf.org>; Thu, 1 Nov 2001 19:41:09 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id fA20f0H10110; Thu, 1 Nov 2001 16:41:00 -0800 (PST)
Message-Id: <200111020041.fA20f0H10110@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3181 on Signaled Preemption Priority Policy Element
Cc: rfc-ed@ISI.EDU, rap@iphighway.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 01 Nov 2001 16:41:00 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
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
Mailbox: herzog@policyconsulting.com
Pages: 12
Characters: 21990
Obsoletes: RFC 2751
I-D Tag: draft-ietf-rap-signaled-priority-v2-01.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3181.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 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
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
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.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.