Internet DRAFT - draft-ietf-policy-terminology
draft-ietf-policy-terminology
A new Request for Comments is now available in online RFC libraries.
RFC 3198
Title: Terminology for Policy-Based Management
Author(s): A. Westerinen, J. Schnizlein, J. Strassner,
M. Scherling, B. Quinn, S. Herzog, A. Huynh,
M. Carlson, J. Perry, S. Waldbusser
Status: Informational
Date: November 2001
Mailbox: andreaw@cisco.com, john.schnizlein@cisco.com,
john.strassner@intelliden.com,
mscherling@xcert.com, bquinn@celoxnetworks.com,
jay.perry@netapp.com, herzog@PolicyConsulting.com,
mark.carlson@sun.com, waldbusser@nextbeacon.com
Pages: 21
Characters: 47806
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-policy-terminology-04.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3198.txt
This document is a glossary of policy-related terms. It
provides abbreviations, explanations, and recommendations for
use of these terms. The document takes the approach and format
of RFC 2828, which defines an Internet Security Glossary.
The intent is to improve the comprehensibility and consistency
of writing that deals with network policy, particularly Internet
Standards documents (ISDs).
This document is a product of the Policy Framework Working Group of
the IETF.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. 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.