idnits 2.17.1 draft-ietf-policy-core-info-model-08.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 3060 5 Title: Policy Core Information Model -- Version 1 6 Specification 7 Author(s): B. Moore, E. Ellesson, J. Strassner, A. Westerinen 8 Status: Standards Track 9 Date: February 2001 10 Mailbox: eellesson@lboard.com, remoore@us.ibm.com, 11 johns@cisco.com, andreaw@cisco.com 12 Pages: 100 13 Characters: 240309 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-policy-core-info-model-08.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3060.txt 20 This document presents the object-oriented information model for 21 representing policy information developed jointly in the IETF Policy 22 Framework WG and as extensions to the Common Information Model (CIM) 23 activity in the Distributed Management Task Force (DMTF). This model 24 defines two hierarchies of object classes: structural classes 25 representing policy information and control of policies, and 26 association classes that indicate how instances of the structural 27 classes are related to each other. Subsequent documents will define 28 mappings of this information model to various concrete 29 implementations, for example, to a directory that uses LDAPv3 as its 30 access protocol. 32 This document is a product of the Policy Framework Working Group of 33 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.