idnits 2.17.1 draft-ietf-rap-sppi-07.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 3159 5 Title: Structure of Policy Provisioning Information 6 (SPPI) 7 Author(s): K. McCloghrie, M. Fine, J. Seligson, K. Chan, 8 S. Hahn, R. Sahita, A. Smith, F. Reichmeyer 9 Status: Standards Track 10 Date: August 2001 11 Mailbox: kzm@cisco.com, mfine@cisco.com, 12 jseligso@nortelnetworks.com, 13 khchan@nortelnetworks.com, 14 scott.hahn@intel.com, ravi.sahita@intel.com, 15 andrew@allegronetworks.com, franr@pfn.com 16 Pages: 40 17 Characters: 78621 18 Obsoletes/Updates/SeeAlso: None 20 I-D Tag: draft-ietf-rap-sppi-07.txt 22 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3159.txt 24 This document, the Structure of Policy Provisioning Information 25 (SPPI), defines the adapted subset of SNMP's Structure of Management 26 Information (SMI) used to write Policy Information Base (PIB) modules. 28 RFC 2748 defines the COPS protocol, and RFC 2749 describes how the 29 COPS protocol is used to provide for the outsourcing of policy 30 decisions for RSVP. Another usage of the COPS protocol, for 31 the provisioning of policy, is introduced in RFC 3084. In 32 this provisioning model, the policy information is viewed as a 33 collection of Provisioning Classes (PRCs) and Provisioning Instances 34 (PRIs) residing in a virtual information store, termed the Policy 35 Information Base (PIB). Collections of related Provisioning Classes 36 are defined in a PIB module. 38 This document is a product of the Resource Allocation Protocol Working 39 Group of the IETF. 41 This is now a Proposed Standard Protocol. 43 This document specifies an Internet standards track protocol for 44 the Internet community, and requests discussion and suggestions 45 for improvements. Please refer to the current edition of the 46 "Internet Official Protocol Standards" (STD 1) for the 47 standardization state and status of this protocol. Distribution 48 of this memo is unlimited. 50 This announcement is sent to the IETF list and the RFC-DIST list. 51 Requests to be added to or deleted from the IETF distribution list 52 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 53 added to or deleted from the RFC-DIST distribution list should 54 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 56 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 57 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 58 help: ways_to_get_rfcs. For example: 60 To: rfc-info@RFC-EDITOR.ORG 61 Subject: getting rfcs 63 help: ways_to_get_rfcs 65 Requests for special distribution should be addressed to either the 66 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 67 specifically noted otherwise on the RFC itself, all RFCs are for 68 unlimited distribution.echo 69 Submissions for Requests for Comments should be sent to 70 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 71 Authors, for further information.