As per Relevance of the word terminology, we have this rfc below:
Network Working Group A.
Request for Comments: 3198 J.
Category: Informational Cisco
J.
Intelliden
M.
B.
Celox
S.
A.
Lucent
M.
Sun
J.
Network
S.
November 2001
Terminology for Policy-Based
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
This document is a glossary of policy-related terms. It
abbreviations, explanations, and recommendations for use of
terms. The document takes the approach and format of RFC 2828,
defines an Internet Security Glossary. The intent is to improve
comprehensibility and consistency of writing that deals with
policy, particularly Internet Standards documents (ISDs).
Westerinen, et al. Informational [Page 1]
RFC 3198 Terminology for Policy-Based Management November 2001
Table of
1. Introduction................................................... 2
2. Explanation of Paragraph Markings.............................. 3
3. Terms.......................................................... 3
4. Intellectual Property.......................................... 16
5. Acknowledgements............................................... 17
6. Security Considerations........................................ 17
7. References..................................................... 17
8. Authors' Addresses............................................. 19
9. Full Copyright Statement....................................... 21
1.
This document provides abbreviations, definitions, and
of terms related to network policy. All definitions are provided
Section 3, with the terms listed in alphabetical order
The intent is to improve the comprehensibility and consistency
Internet Standards documents (ISDs) -- i.e., RFCs, Internet-Drafts
and other material produced as part of the Internet Standards
[RFC2026]. Benefits across the ISDs are well-stated in
Introduction to RFC 2828 [RFC2828]:
o "Clear, Concise, and Easily Understood Documentation" -
that the set of terms and definitions be consistent, self
supporting and uniform across all ISDs
o Technical Excellence - Where all ISDs use terminology accurately
precisely, and unambiguously
o Prior Implementation and Testing - Requires that terms are used
their plainest form, that private and "made-up" terms are
in ISDs, and that new definitions are not created that
with established ones
o "Openness, Fairness, and Timeliness" - Where ISDs avoid terms
are proprietary or otherwise favor a particular vendor, or
create a bias toward a particular technology or mechanism
Common and/or controversial policy terms are defined. These
are directly related and specific to network policy
Wherever possible, this document takes definitions from
ISDs. It should be noted that
o Expired Internet-Drafts are not referenced, nor are
terminology and definitions used in this document
Westerinen, et al. Informational [Page 2]
RFC 3198 Terminology for Policy-Based Management November 2001
o Multiple definitions may exist across the ISDs. Each
is listed, with its source
2. Explanation of Paragraph
Section 3 marks terms and definitions as follows
o Capitalization: Only terms that are proper nouns are capitalized
o Paragraph Marking: Definitions and explanations are stated
paragraphs that are marked as follows
- "P" identifies basic policy-related terms
- "T" identifies various techniques to create or convey policy
related information in a network. For example, COPS and
"Information Model" are two techniques for communicating
describing policy-related data. SNMP and MIBs are another
- "A" identifies specific Work Groups and general "areas of use
of policy. For example, AAA and QoS are two "areas of use
where policy concepts are extremely important to their
and operation
3.
Note: In providing policy definitions, other "technology specific
terms (for example, related to Differentiated Services) may be
and referenced. These non-policy terms will not be defined in
document, and the reader is requested to go to the referenced ISD
additional detail
$
See "Authentication, Authorization, Accounting".
$ abstraction
See "policy abstraction".
$
See "policy action".
$ Authentication, Authorization, Accounting (AAA
(A) AAA deals with control, authentication, authorization
accounting of systems and environments based on policies
by the administrators and users of the systems. The use
policy may be implicit - as defined by RADIUS [RFC2138].
RADIUS, a network access server sends dial-user credentials
an AAA server, and receives authentication that the user
Westerinen, et al. Informational [Page 3]
RFC 3198 Terminology for Policy-Based Management November 2001
who he/she claims, along with a set of attribute-value
authorizing various service features. Policy is implied
both the authentication, which can be restricted by time
day, number of sessions, calling number, etc., and
attribute-values authorized
$
See "Common Information Model".
$ Common Information Model (CIM
(T) An object-oriented information model published by the
(Distributed Management Task Force) [DMTF]. It consists of
Specification detailing the abstract modeling constructs
principles of the Information Model, and a textual
definition to represent the Model. CIM's schemas are
as a set of files, written in the language of
Specification, with graphical renderings using UML [UML].
Sets of classes and associations represent CIM's Core
Common Models, defining an information model for
"enterprise" - addressing general concepts (in Core),
systems, devices, users, software distribution, the
environment, networks and policy (in the Common Models). (
also "information model".)
$ Common Open Policy Service (COPS
(T) A simple query and response TCP-based protocol that can
used to exchange policy information between a Policy
Point (PDP) and its clients (Policy Enforcement Points, PEPs
[RFC2748]. The COPS protocol is used to provide for
outsourcing of policy decisions for RSVP [RFC2749].
usage is for the provisioning of policy [RFC3084]. (See
"Policy Decision Point" and "Policy Enforcement Point".)
$
See "policy condition".
$
(P) "Configuration" can be defined from two perspectives
- The set of parameters in network elements and other
that determine their function and operation.
parameters are static, such as packet queue assignment
can be predefined and downloaded to a network element
Others are more dynamic, such as the actions taken by
network device upon the occurrence of some event.
distinction between static (predefined) "configuration"
the dynamic state of network elements blurs as
parameters becomes more responsive, and signaling
greater degrees of a network device's behavior
Westerinen, et al. Informational [Page 4]
RFC 3198 Terminology for Policy-Based Management November 2001
- A static setup of a network element, done before
to a customer and which cannot be modified by the customer
The first is the accepted usage in the Internet community
$
See "Common Open Policy Service".
$ data
(T) A mapping of the contents of an information model into a
that is specific to a particular type of data store
repository. A "data model" is basically the rendering of
information model according to a specific set of
for representing, organizing, storing and handling data.
has three parts [DecSupp]:
- A collection of data structures such as lists, tables
relations, etc
- A collection of operations that can be applied to
structures such as retrieval, update, summation, etc
- A collection of integrity rules that define the
states (set of values) or changes of state (operations
values).
(See also "information model".)
$
See "Directory Enabled Networks".
$ Differentiated Services (DS
(T) The IP header field, called the DS-field. In IPv4, it
the layout of the ToS (Type of Service) octet; in IPv6, it
the Traffic Class octet [RFC2474].
(A) "Differentiated Services" is also an "area of use" for
policies. It requires policy to define the
between codepoints in the packet's DS-field and
per-hop behaviors (to achieve a specified per-
behavior). In addition, policy can be used to specify
routing of packets based on various classification criteria
(See also "Quality of Service" and "filter".)
$
See "Differentiated Services".
$ Directory Enabled Networks (DEN
(T) A data model that is the LDAP mapping of CIM (the
Information Model). Its goals are to enable the
and use of policy by starting with common service and
concepts (defined in the information model), specifying
Westerinen, et al. Informational [Page 5]
RFC 3198 Terminology for Policy-Based Management November 2001
mapping/storage in an LDAP-based repository, and using
concepts in vendor/device-independent policy rules [DMTF].
(See also "Common Information Model" and "data model".)
$
(P) A collection of elements and services, administered in
coordinated fashion. (See also "policy domain".)
$
See "Differentiated Services".
$
(T) A set of terms and/or criteria used for the purpose
separating or categorizing. This is accomplished via single
or multi-field matching of traffic header and/or payload data
"Filters" are often manipulated and used in network
and policy. For example, packet filters specify the
for matching a pattern (for example, IP or 802 criteria)
distinguish separable classes of traffic
$
See "policy goal".
$ information
(T) An abstraction and representation of the entities in a
environment, their properties, attributes and operations,
the way that they relate to each other. It is independent
any specific repository, software usage, protocol,
platform
$ Management Information Base (MIB
(T) A collection of information that can be accessed via
Simple Network Management Protocol. Management information
defined in MIB modules using the rules contained in SNMP'
Structure of Management Information (SMI)
[RFC2570]. Management information is an abstract concept,
definitions can be created for high level
specifications, low level policy, as well as technology
vendor specific configurations, status and statistics. (
also "Simple Network Management Protocol" and "Structure
Management Information".)
$
See "Management Information Base".
Westerinen, et al. Informational [Page 6]
RFC 3198 Terminology for Policy-Based Management November 2001
$
See "Multiprotocol Label Switching". (Also, MPLS may refer
Multi-Protocol Lambda Switching in optical networks. But, this
unrelated to policy and not discussed further in this document.)
$ Multiprotocol Label Switching (MPLS
(T) Integrates a label swapping and switching framework
network layer routing [RFC2702]. The basic idea
assigning short fixed length labels to packets at the
to an MPLS cloud. Throughout the interior of the MPLS domain
the labels attached to packets are used to make
decisions (usually without recourse to the original
headers).
$ outsourced
(P) An execution model where a policy enforcement device issues
query to delegate a decision for a specific policy event
another component, external to it. For example, in RSVP,
arrival of a new RSVP message to a PEP requires a fast
decision (not to delay the end-to-end setup). The PEP may
COPS-RSVP to send a query to the PDP, asking for a
decision [RFC2205, RFC2748]. "Outsourced policy"
contrasted with "provisioned policy", but they are
mutually exclusive and operational systems may combine
two
$
See "Policy Core Information Model".
$
See "Policy Decision Point".
$
See "Policy Enforcement Point".
$
See "Policy Information Base".
$
(P) "Policy" can be defined from two perspectives
- A definite goal, course or method of action to guide
determine present and future decisions. "Policies"
implemented or executed within a particular context (
as policies defined within a business unit).
- Policies as a set of rules to administer, manage,
control access to network resources [RFC3060].
Westerinen, et al. Informational [Page 7]
RFC 3198 Terminology for Policy-Based Management November 2001
Note that these two views are not contradictory
individual rules may be defined in support of business goals
(See also "policy goal", "policy abstraction" and "
rule".)
$ policy
(P) Policy can be represented at different levels, ranging
business goals to device-specific configuration parameters
Translation between different levels of "abstraction"
require information other than policy, such as network
host parameter configuration and capabilities.
documents and implementations may specify explicit levels
abstraction. However, these do not necessarily correspond
distinct processing entities or the complete set of levels
all environments. (See also "configuration" and "
translation".)
$ policy
(P) Definition of what is to be done to enforce a policy rule
when the conditions of the rule are met. Policy actions
result in the execution of one or more operations to
and/or configure network traffic and network resources
- In [RFC3060], a rule's actions may be ordered
$ policy
(P) A representation of the necessary state and/or
that define whether a policy rule's actions should
performed. This representation need not be
specified, but may be implicitly provided in an
or protocol. When the policy condition(s) associated with
policy rule evaluate to TRUE, then (subject to
considerations such as rule priorities and
strategies) the rule should be enforced
(T) In [RFC3060], a rule's conditions can be expressed as
an ORed set of ANDed sets of statements (disjunctive
form), or an ANDed set of ORed sets of statements (
normal form). Individual condition statements can also
negated
$ policy
(P) Occurs when the actions of two rules (that are both
simultaneously) contradict each other. The
implementing the policy would not be able to determine
action to perform. The implementers of policy systems
provide conflict detection and avoidance or
mechanisms to prevent this situation. "Policy conflict"
contrasted with "policy error".
Westerinen, et al. Informational [Page 8]
RFC 3198 Terminology for Policy-Based Management November 2001
$ policy
See "policy translation".
$ Policy Core Information Model (PCIM) [RFC3060]
(T) An information model describing the basic concepts of
groups, rules, conditions, actions, repositories and
relationships. This model is described as a "core"
since it cannot be applied without domain-specific
(for example, extensions for QoS or IPsec). PCIM is "core
with respect to the area of policy. However, it is a "
Model," with respect to CIM - in that it extends the basic
concepts for policy. (See also "Common Information Model".)
$ policy
(P) Two perspectives of "policy decision" exist
- A "process" perspective that deals with the evaluation of
policy rule's
- A "result" perspective that deals with the actions
enforcement, when the conditions of a policy rule are
$ Policy Decision Point (PDP
(P) A logical entity that makes policy decisions for itself or
other network elements that request such decisions [RFC2753].
(See also "policy decision".)
$ policy
(P) A collection of elements and services, and/or a portion of
Internet over which a common and consistent set of
are administered in a coordinated fashion [RFC2474].
definition of a policy domain does not preclude
sources of policy creation within an organization, but
require that the resultant policies be coordinated
- Policies defined in the context of one domain may need
be communicated or negotiated outside of that domain. (
also "policy negotiation".)
$ policy
(P) The execution of a policy decision
$ Policy Enforcement Point (PEP
(P) A logical entity that enforces policy decisions [RFC2753].
(See also "policy enforcement".)
$ policy
(P) "Policy errors" occur when attempts to enforce policy
fail, whether due to temporary state or permanent
between the policy actions and the device
capabilities. This is contrasted with "policy conflict".
Westerinen, et al. Informational [Page 9]
RFC 3198 Terminology for Policy-Based Management November 2001
$ policy
(P) Goals are the business objectives or desired state intended
be maintained by a policy system. As the highest level
abstraction of policy, these goals are most directly
in business rather than technical terms. For example, a
might state that a particular application operate on a
as though it had its own dedicated network, despite using
shared infrastructure. 'Policy goals' can include
objectives of a service level agreement, as well as
assignment of resources to applications or individuals.
policy system may be created that automatically strives
achieve a goal through feedback regarding whether the
(such as a service level) is being met
$ Policy Information Base (PIB
(T) Collections of related PRovisioning Classes (PRCs), defined
a module. (See also "PRovisioning Class".)
$ policy
See "policy translation".
$ policy
(P) Exposing the desired or appropriate part of a policy
another domain. This is necessary to support
interconnection between domains, which are operating
different sets of policies
$ policy
(P) "Policy repository" can be defined from three perspectives
- A specific data store that holds policy rules,
conditions and actions, and related policy data.
database or directory would be an example of such a store
- A logical container representing the administrative
and naming of policy rules, their conditions and actions
and related policy data. A "QoS policy" domain would be
example of such a container
- In [RFC3060], a more restrictive definition than the
one exists. A PolicyRepository is a model
representing an administratively defined, logical
for reusable policy elements
$ policy
(P) A message requesting a policy-related service. This may
to a request to retrieve a specific set of policy rules,
determine the actions to enforce, or other policy requests
When sent by a PEP to a PDP, it is more accurately
as a "policy decision request" [RFC2753]. (See also "
decision".)
Westerinen, et al. Informational [Page 10]
RFC 3198 Terminology for Policy-Based Management November 2001
$ policy
(P) A basic building block of a policy-based system. It is
binding of a set of actions to a set of conditions - where
conditions are evaluated to determine whether the actions
performed [RFC3060].
$ policy
(P) A marketing term whose definition is imprecise. Originally
[RFC2753] referenced a "policy server". As the RFC evolved
this term became more precise and known as the Policy
Point (PDP). Today, the term is used in marketing and
literature to refer specifically to a PDP, or for any
that uses/services policy
$ policy
(P) The transformation of a policy from a representation and/
level of abstraction, to another representation or level
abstraction. For example, it may be necessary to convert
data to a command line format. In this "conversion,"
translation to the new representation is likely to require
change in the level of abstraction (becoming more or
specific). Although these are logically distinct tasks,
are (in most cases) blurred in the act
translating/converting/mapping. Therefore, this is also
as "policy conversion" or "policy mapping".
$
(T) An abstraction in the Policy Core Information Model [RFC3060].
It is a class representing a container, aggregating
policy rules or other policy groups. It allows the
of rules into a Policy, and the refinement of high-
Policies to lower-level or different (i.e., converted
translated) peer groups
$
See "PRovisioning Class".
$
See "PRovisioning Instance".
$ provisioned
(P) An execution model where network elements are pre-configured
based on policy, prior to processing events. Configuration
pushed to the network device, e.g., based on time of day or
initial booting of the device. The focus of this model is
the distribution of configuration information, and
exemplified by Differentiated Services [RFC2475]. Based
events received, devices use downloaded (pre-provisioned
Westerinen, et al. Informational [Page 11]
RFC 3198 Terminology for Policy-Based Management November 2001
mechanisms to implement policy. "Provisioned policy"
contrasted with "outsourced policy".
$ PRovisioning Class (PRC
(T) An ordered set of attributes representing a type of
data. PRCs are defined in PIB modules (encoded using SPPI
and registered in the Object Identifier tree. Instances
each PRC are organized in tables, similar to conceptual
in SMIv2. (See also "Structure of Policy
Information" and "Policy Information Base".)
The acronym, PRC, has evolved from "policy rule class"
"provisioning class". The reason for the change is that
discrepancy existed between the use of the words, "
rule" in the PRC context versus other uses in PCIM and
industry. In the latter, rules are If/Then statements -
binding of conditions to actions. PRCs are not "rules"
this definition, but the encoding of (network-wide
configuration information for a device
$ PRovisioning Instance (PRI
(T) An instantiation of a PRovisioning Class. (See
"PRovisioning Class".)
$
See "Quality of Service".
$ Quality of Service (QoS
(A) At a high level of abstraction, "Quality of Service" refers
the ability to deliver network services according to
parameters specified in a Service Level Agreement. "Quality
is characterized by service availability, delay, jitter
throughput and packet loss ratio. At a network
level, "Quality of Service" refers to a set of
that allow a service provider to prioritize traffic,
bandwidth, and network latency. There are two
approaches to "Quality of Service" on IP networks:
Services [RFC1633], and Differentiated Service [RFC2475].
Integrated Services require policy control over the
of signaled reservations, which provide specific
end-to-end behavior for a (set of) flow(s). In contrast
Differentiated Services require policy to define
correspondence between codepoints in the packet's DS-field
individual per-hop behaviors (to achieve a specified per
domain behavior). A maximum of 64 per-hop behaviors limit
number of classes of service traffic that can be marked at
point in a domain. These classes of service signal
treatment of the packets with respect to various QoS aspects
such as flow priority and packet drop precedence.
Westerinen, et al. Informational [Page 12]
RFC 3198 Terminology for Policy-Based Management November 2001
addition, policy can be used to specify the routing of
based on various classification criteria. Policy controls
set of configuration parameters and routing for each class
Differentiated Service, and the admission conditions
reservations in Integrated Services. (See also "
abstraction" and "Service Level Agreement".)
$ Resource reSerVation Protocol (RSVP
(T) A setup protocol designed for an Integrated Services Internet
to reserve network resources for a path [RFC2205]. And,
signaling mechanism for managing application traffic's QoS
a Differentiated Service network
$
(P) "Role" is defined from three perspectives
- A business position or function, to which people
logical entities are assigned [X.500]
- The labeled endpoints of a UML (Unified Modeling Language
association. Quoting from [UML], "When a
participates in an association, it has a specific role
it plays in that relationship; a role is just the face
class at the near end of the association presents to
class at the other end of the association". The
Core Information Model [RFC3060] uses UML to depict
class hierarchy. Relationships/associations are
in the model
- An administratively specified characteristic of a
element (for example, an interface). It is a selector
policy rules and PRovisioning Classes (PRCs), to
the applicability of the rule/PRC to a particular
element [RFC3060].
Only the third definition (roles as selectors of policy)
directly related to the management of network policy. However
the first definition (roles as business positions
functions) may be referenced in policy conditions and actions
$ role
(P) A lexicographically ordered set of roles that
managed elements and indicate the applicability of
rules and PRovisioning Classes (PRCs). A policy system
the set of roles reported by the managed element to
the correct rules/PRCs to be sent for enforcement.
determination may examine all applicable policy
identified by the role combination, its sub-combinations
the individual roles in the combination [RFC3060]. In
case of PRCs, a PRC must explicitly match the role
of the managed element in order to be applicable and/
enforced. (The comparison is typically case-sensitive.)
Westerinen, et al. Informational [Page 13]
RFC 3198 Terminology for Policy-Based Management November 2001
final set of rules/PRCs for enforcement are defined by
policy system, as appropriate for the specified
combination of the managed element
$
See "Resource reSerVation Protocol".
$
See "policy rule".
$ rule based
(T) A rule based engine is able to evaluate policy condition(s
and trigger appropriate policy actions. A particular
based engine may only be capable of acting upon policy
that are formatted in a specified way or adhere to a
language
$
(T) Two different perspectives of schema are defined
- A set of rules that determines what data can be stored in
database or directory service [DirServs
- A collection of data models that are each bound to the
type of repository
The latter is the preferred and recommended one for
Standards documents. (See also "data model".)
$
(P) The behavior or functionality provided by a network,
element or host [DMTF, RFC2216]. Quoting from RFC 2216
[RFC2216], in order to completely specify a "service",
must define the "functions to be performed ...,
information required ... to perform these functions, and
information made available by the element to other elements
the system". Policy can be used to configure a "service" in
network or on a network element/host, invoke
functionality, and/or coordinate services in an interdomain
end-to-end environment
$ Service Level Agreement (SLA
(P) The documented result of a negotiation between
customer/consumer and a provider of a service, that
the levels of availability, serviceability, performance
operation or other attributes of the service [RFC2475]. (
also "Service Level Objective".)
Westerinen, et al. Informational [Page 14]
RFC 3198 Terminology for Policy-Based Management November 2001
$ Service Level Objective (SLO
(P) Partitions an SLA into individual metrics and
information to enforce and/or monitor the SLA. "Service
Objectives" may be defined as part of an SLA, an SLS, or in
separate document. It is a set of parameters and
values. The actions of enforcing and reporting
compliance can be implemented as one or more policies. (
also "Service Level Agreement".)
$ Service Level Specification (SLS
(P) Specifies handling of customer's traffic by a
provider. It is negotiated between a customer and
provider, and (for example) in a DiffServ environment,
parameters such as specific Code Points and the Per-Hop
Behavior, profile characteristics and treatment of the
for those Code Points. An SLS is a specific SLA (a
agreement) and its SLOs (the individual metrics
operational data to enforce) to guarantee quality of
for network traffic. (See also "Service Level Agreement"
"Service Level Objective".)
$ Simple Network Management Protocol (SNMP
(T) SNMP is a framework (including a protocol) for
systems in a network environment [RFC2570]. It can be
for policy-based configuration and control using a
MIB Module designed to execute policies on managed
via scripts. The elements (instances) in a network device
evaluated using a policy filter, to determine where
will be applied
$
See "Service Level Agreement".
$
See "Service Level Objective".
$
See "Service Level Specification".
$ SMIv
See "Structure of Management Information".
$
See "Simple Network Management Protocol".
$
See "Structure of Policy Provisioning Information".
Westerinen, et al. Informational [Page 15]
RFC 3198 Terminology for Policy-Based Management November 2001
$ Structure of Policy Provisioning Information (SPPI
(T) An adapted subset of SNMP's Structure of
Information (SMIv2) that is used to encode collections
related PRovisioning Classes as a PIB [RFC3159]. (See
"Policy Information Base" and "PRovisioning Class".)
$ Structure of Management Information, version 2 (SMIv2)
(T) An adapted subset of OSI's Abstract Syntax Notation One, ASN.1
(1988) used to encode collections of related objects as
Management Information Base (MIB) modules [RFC2578].
$
(P) An entity, or collection of entities, which originates
request, and is verified as authorized/not authorized
perform that request
$
(P) An entity, or collection of entities, which is affected by
policy. For example, the "targets" of a policy to
a network device are the individual services that are
and configured
4. Intellectual
The IETF takes no position regarding the validity or scope of
intellectual property or other rights that might be claimed
pertain to the implementation or use of the technology described
this document or the extent to which any license under such
might or might not be available; neither does it represent that
has made any effort to identify any such rights. Information on
IETF's procedures with respect to rights in standards-track
standards-related documentation can be found in BCP-11.
Copies of claims of rights made available for publication and
assurances of licenses to be made available, or the result of
attempt made to obtain a general license or permission for the use
such proprietary rights by implementers or users of
specification can be obtained from the IETF Secretariat
The IETF invites any interested party to bring to its attention
copyrights, patents or patent applications, or other
rights which may cover technology that may be required to
this standard. Please address the information to the IETF
Director
Westerinen, et al. Informational [Page 16]
RFC 3198 Terminology for Policy-Based Management November 2001
5.
This document builds on the work of previous terminology drafts.
authors of these documents were Fran Reichmeyer, Dan Grossman,
Strassner, Ed Ellesson and Matthew Condell. Also, definitions
the general concepts of policy and policy rule include input
Predrag Spasic. Very helpful comments and suggestions were
from Juergen Schoenwaelder, Joe Salowey, Jon Saperia, Ravi Sahita
Bob Moore, Guus Sliepen, T.H. Jonatan and Dave Perkins
6. Security
This document only defines policy-related terms. It does
describe in detail the vulnerabilities of, threats to, or
that protect specific policy implementations or policy-
Internet protocols
7.
[DecSupp] Building Effective Decision Support Systems. R
Sprague, and E. Carleson. Prentice Hall, 1982.
[DirServs] Understanding and Deploying LDAP Directory Services. T
Howes, M. Smith, and G. Good. MacMillan
Publications, 1999.
[DMTF] Common Information Model (CIM) Schema, version 2.x
Distributed Management Task Force, Inc. The
of the CIM v2.x schema are available via links on
following DMTF web page
http://www.dmtf.org/standards/standard_cim.php
[RFC1633] Braden, R., Clark, D. and S. Shenker, "
Services in the Internet Architecture: An Overview",
1633, June 1994.
[RFC2026] Bradner, S., "The Internet Standards Process --
3", BCP 9, RFC 2026, October 1996.
[RFC2138] Rigney, C., Rubens, A., Simpson, W. and S. Willens
"Remote Authentication Dial In User Service (RADIUS)",
RFC 2138, April 1997.
[RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S. and S
Jamin, "Resource ReSerVation Protocol (RSVP) --
1 Functional Specification", RFC 2205, September 1997.
Westerinen, et al. Informational [Page 17]
RFC 3198 Terminology for Policy-Based Management November 2001
[RFC2216] Shenker, S. and J. Wroclawski, "Network Element
Specification Template", September 1997.
[RFC2474] Nichols, K., Blake, S., Baker, F. and D. Black
"Definition of the Differentiated Services Field (
Field) in the IPv4 and IPv6 Headers", RFC 2474,
1998.
[RFC2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z
and W. Weiss, "An Architecture for
Service", RFC 2475, December 1998.
[RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart
"Introduction to Version 3 of the Internet-
Network Management Framework", RFC 2570, April 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case
J., Rose, M. and S.Waldbusser, "Structure of
Information Version 2 (SMIv2)", RFC 2578, April 1999.
[RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M. and J
McManus, "Requirements for Traffic Engineering
MPLS", RFC 2702, September 1999.
[RFC2748] Durham, D., Boyle, J., Cohen, R., Herzog, S., Rajan, R
and A. Sastry, "The COPS (Common Open Policy Service
Protocol", RFC 2748, January 2000.
[RFC2749] Herzog, S., Boyle, J., Cohen, R., Durham, D., Rajan, R
and A. Sastry, "COPS Usage for RSVP", RFC 2749,
2000.
[RFC2753] Yavatkar, R., Pendarakis, D. and R. Guerin, "A
for Policy-based Admission Control", RFC 2753,
2000.
[RFC2828] Shirey, R., "Internet Security Glossary", FYI 36,
2828, May 2000.
[RFC3060] Moore, B., Ellesson, E., Strassner, J. and A
Westerinen, "Policy Core Information Model -- Version 1
Specification", RFC 3060, February 2001.
[RFC3084] Chan, K., Seligson, J., Durham, D., Gai, S., McCloghrie
K., Herzog, S., Reichmeyer, F., Yavatkar, R. and A
Smith, "COPS Usage for Policy Provisioning (COPS-PR)",
RFC 3084, February 2001.
Westerinen, et al. Informational [Page 18]
RFC 3198 Terminology for Policy-Based Management November 2001
[RFC3159] McCloghrie, K., Fine, M., Seligson, J., Chan, K., Hahn
S., Sahita, R., Smith, A. and F. Reichmeyer, "
of Policy Provisioning Information," RFC 3159,
2001.
[UML] The Unified Modeling Language User Guide. G. Booch, J
Rumbaugh, and I. Jacobson. Addison-Wesley, 1999.
[X.500] Data Communications Networks Directory,
X.500-X.521, Volume VIII - Fascicle VIII.8. CCITT,
Plenary Assembly, Melbourne. November 1988.
8. Authors'
Andrea
Cisco Systems, Bldg 20
725 Alder
Milpitas, CA 95035
EMail: andreaw@cisco.
John
Cisco
9123 Loughran
Fort Washington, MD 20744
EMail: john.schnizlein@cisco.
John
Intelliden
90 South Cascade
Colorado Springs, CO 80903
Phone: +1-719-785-0648
EMail: john.strassner@intelliden.
Mark
Xcert International Inc
Suite 300
505 Burrard
Vancouver,
V7X 1M
EMail: mscherling@xcert.
Westerinen, et al. Informational [Page 19]
RFC 3198 Terminology for Policy-Based Management November 2001
Bob
Celox
2 Park Central
Southborough, MA 01772
EMail: bquinn@celoxnetworks.
Jay
Network
495 East Java
Sunnyvale, CA 94089
EMail: jay.perry@netapp.
Shai
PolicyConsulting.
200 Clove Rd
New Rochelle, NY 10801
EMail: herzog@PolicyConsulting.
An-Ni
Lucent
2139 Route 35
Holmdel, NJ 07733
Mark
Sun Microsystems, Inc
500 Eldorado
Broomfield, CO 80021
EMail: mark.carlson@sun.
Steve
Phone: +1-650-948-6500
Fax: +1-650-745-0671
EMail: waldbusser@nextbeacon.
Westerinen, et al. Informational [Page 20]
RFC 3198 Terminology for Policy-Based Management November 2001
9. Full Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Westerinen, et al. Informational [Page 21]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
