COPS Usage for Policy Provisioning
draft-sgai-cops-provisioning-00

Document Type Expired Internet-Draft (individual)
Authors Kwok Chan  , Silvano Gai  , Shai Herzog  , Keith McCloghrie , Francis Reichmeyer  , Andrew Smith  , Raj Yavatkar 
Last updated 1999-03-02
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-sgai-cops-provisioning-00.txt

Abstract

There is a clear need for a standard way to provision policies to network devices. These policies may be related to QoS (Quality of Service), Security, VPNs (Virtual Private Networks), etc. The IETF RSVP Admission Policy (RAP) WG has defined the COPS (Common Open Policy Service) protocol [COPS] and a scalable policy control model for RSVP [RSVP]. This document describes a new client type ('Provisioning') for the Common Open Policy Service (COPS) protocol to support policy provisioning. This new client type is independent of the type of policy and it is based on the concept of PIBs (Policy Information Bases [PIB]. The example of provisioning used in this document is QoS Policy Provisioning in a Differentiated Services (DiffServ) environment.

Authors

Kwok Chan (khchan@BayNetworks.com)
Silvano Gai (sgai@nuovasystems.com)
Shai Herzog (herzog@iphighway.com)
Keith McCloghrie (kzm@cisco.com)
Francis Reichmeyer (freichmeyer@baynetworks.com)
Andrew Smith (ah_smith@pacbell.net)
Raj Yavatkar (raj.yavatkar@intel.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)