Policy Core Information Model -- Version 1 Specification
The information below is for an old version of the document that is already published as an RFC.
This is an older version of an Internet-Draft that was ultimately published as RFC 3060.
|Authors||Dr. Robert C. Moore , John Strassner , Ed J. Ellesson , Andrea Westerinen|
|Last updated||2013-03-02 (Latest revision 2000-10-13)|
|RFC stream||Internet Engineering Task Force (IETF)|
|Additional resources||Mailing list discussion|
|This information refers to IESG processing after the RFC was initially published:|
|IESG||IESG state||RFC 3060 (Proposed Standard)|
|Responsible AD||Bert Wijnen|
|Send notices to||<Sandra_murphy@nai.com>|
A new Request for Comments is now available in online RFC libraries. RFC 3060 Title: Policy Core Information Model -- Version 1 Specification Author(s): B. Moore, E. Ellesson, J. Strassner, A. Westerinen Status: Standards Track Date: February 2001 Mailbox: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com Pages: 100 Characters: 240309 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-policy-core-info-model-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3060.txt This document presents the object-oriented information model for representing policy information developed jointly in the IETF Policy Framework WG and as extensions to the Common Information Model (CIM) activity in the Distributed Management Task Force (DMTF). This model defines two hierarchies of object classes: structural classes representing policy information and control of policies, and association classes that indicate how instances of the structural classes are related to each other. Subsequent documents will define mappings of this information model to various concrete implementations, for example, to a directory that uses LDAPv3 as its access protocol. This document is a product of the Policy Framework Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information.