idnits 2.17.1 draft-ietf-rap-pr-05.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 3084 5 Title: COPS Usage for Policy Provisioning (COPS-PR) 6 Author(s): K. Chan, J. Seligson, D. Durham, S. Gai, 7 K. McCloghrie, S. Herzog, F. Reichmeyer, 8 R. Yavatkar, A. Smith 9 Status: Standards Track 10 Date: March 2001 11 Mailbox: khchan@nortelnetworks.com, david.durham@intel.com, 12 sgai@cisco.com, Herzog@iphighway.com, 13 kzm@cisco.com, franr@pfn.com, 14 jseligso@nortelnetworks.com, 15 raj.yavatkar@intel.com, andrew@allegronetworks.com 17 Pages: 34 18 Characters: 79341 19 Updates/Obsoletes/SeeAlso: None 21 I-D Tag: draft-ietf-rap-pr-05.txt 23 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3084.txt 25 This document describes the use of the Common Open Policy Service 26 (COPS) protocol for support of policy provisioning (COPS-PR). This 27 specification is independent of the type of policy being provisioned 28 (QoS, Security, etc.) but focuses on the mechanisms and conventions 29 used to communicate provisioned information between PDPs and PEPs. 30 The protocol extensions described in this document do not make any 31 assumptions about the policy data model being communicated, but 32 describe the message formats and objects that carry the modeled policy 33 data. 35 This document is a product of the Resource Allocation Protocol Working 36 Group of IETF. 38 This is now a Proposed Standard Protocol. 40 This document specifies an Internet standards track protocol for 41 the Internet community, and requests discussion and suggestions 42 for improvements. Please refer to the current edition of the 43 "Internet Official Protocol Standards" (STD 1) for the 44 standardization state and status of this protocol. Distribution 45 of this memo is unlimited. 47 This announcement is sent to the IETF list and the RFC-DIST list. 48 Requests to be added to or deleted from the IETF distribution list 49 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 50 added to or deleted from the RFC-DIST distribution list should 51 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 53 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 54 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 55 help: ways_to_get_rfcs. For example: 57 To: rfc-info@RFC-EDITOR.ORG 58 Subject: getting rfcs 60 help: ways_to_get_rfcs 62 Requests for special distribution should be addressed to either the 63 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 64 specifically noted otherwise on the RFC itself, all RFCs are for 65 unlimited distribution.echo 66 Submissions for Requests for Comments should be sent to 67 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 68 Authors, for further information.