idnits 2.17.1 draft-ietf-rap-signaled-priority-v2-01.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3181 5 Title: Signaled Preemption Priority Policy Element 6 Author(s): S. Herzog 7 Status: Standards Track 8 Date: October 2001 9 Mailbox: herzog@policyconsulting.com 10 Pages: 12 11 Characters: 21990 12 Obsoletes: RFC 2751 14 I-D Tag: draft-ietf-rap-signaled-priority-v2-01.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3181.txt 18 This document describes a preemption priority policy element for use 19 by signaled policy based admission protocols (such as the Resource 20 ReSerVation Protocol (RSVP) and Common Open Policy Service (COPS). 22 Preemption priority defines a relative importance (rank) within the 23 set of flows competing to be admitted into the network. Rather than 24 admitting flows by order of arrival (First Come First Admitted) 25 network nodes may consider priorities to preempt some previously 26 admitted low priority flows in order to make room for a newer, 27 high-priority flow. 29 This memo corrects an RSVP POLICY_DATA P-Type codepoint assignment 30 error in RFC 2751. 32 This document is a product of the Resource Allocation Protocol Working 33 Group of the IETF. 35 This is now a Proposed Standard Protocol. 37 This document specifies an Internet standards track protocol for 38 the Internet community, and requests discussion and suggestions 39 for improvements. Please refer to the current edition of the 40 "Internet Official Protocol Standards" (STD 1) for the 41 standardization state and status of this protocol. Distribution 42 of this memo is unlimited. 44 This announcement is sent to the IETF list and the RFC-DIST list. 45 Requests to be added to or deleted from the IETF distribution list 46 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 47 added to or deleted from the RFC-DIST distribution list should 48 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 50 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 51 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 52 help: ways_to_get_rfcs. For example: 54 To: rfc-info@RFC-EDITOR.ORG 55 Subject: getting rfcs 57 help: ways_to_get_rfcs 59 Requests for special distribution should be addressed to either the 60 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 61 specifically noted otherwise on the RFC itself, all RFCs are for 62 unlimited distribution.echo 63 Submissions for Requests for Comments should be sent to 64 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 65 Authors, for further information.