idnits 2.17.1 draft-ietf-rap-frameworkpib-09.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 3318 5 Title: Framework Policy Information Base 6 Author(s): R. Sahita, Ed., S. Hahn, K. Chan, K. McCloghrie 7 Status: Informational 8 Date: March 2003 9 Mailbox: ravi.sahita@intel.com, scott.hahn@intel.com, 10 khchan@nortelnetworks.com, kzm@cisco.com 11 Pages: 70 12 Characters: 144530 13 Updates/Obsoletes/See Also: None 15 I-D Tag: draft-ietf-rap-frameworkpib-09.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3318.txt 19 This document defines a set of PRovisioning Classes (PRCs) and textual 20 conventions that are common to all clients that provision policy using 21 Common Open Policy Service (COPS) protocol for Provisioning. 23 Structure of Policy Provisioning Information (SPPI) describes a 24 structure for specifying policy information that can then be 25 transmitted to a network device for the purpose of configuring 26 policy at that device. The model underlying this structure is one 27 of well-defined (PRCs) and instances of these 28 classes (PRIs) residing in a virtual information store called the 29 Policy Information Base (PIB). 31 One way to provision policy is by means of the (COPS) protocol with 32 the extensions for provisioning. This protocol supports multiple 33 clients, each of which may provision policy for a specific policy 34 domain such as QoS, virtual private networks, or security. 36 As described in COPS usage for Policy Provisioning (COPS-PR), each 37 client supports a non-overlapping and independent set of PIB 38 modules. However, some PRovisioning Classes are common to all 39 subject-categories (client-types) and need to be present in 40 each. 42 This document is a product of the Resource Access Protocol (RAP) 43 Working Group of the IETF. 45 This memo provides information for the Internet community. It does 46 not specify an Internet standard of any kind. Distribution of this 47 memo is unlimited. 49 This announcement is sent to the IETF list and the RFC-DIST list. 50 Requests to be added to or deleted from the IETF distribution list 51 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 52 added to or deleted from the RFC-DIST distribution list should 53 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 55 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 56 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 57 help: ways_to_get_rfcs. For example: 59 To: rfc-info@RFC-EDITOR.ORG 60 Subject: getting rfcs 62 help: ways_to_get_rfcs 64 Requests for special distribution should be addressed to either the 65 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 66 specifically noted otherwise on the RFC itself, all RFCs are for 67 unlimited distribution.echo 68 Submissions for Requests for Comments should be sent to 69 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 70 Authors, for further information.