COPS Usage for Policy Provisioning
draft-sgai-cops-provisioning-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Kwok H. Chan , Silvano Gai , Shai Herzog , Keith McCloghrie, Francis Reichmeyer , Andrew H. Smith , Dr. Raj Yavatkar | ||
Last updated | 1999-03-02 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 H. Chan
Silvano Gai
Shai Herzog
Keith McCloghrie
Francis Reichmeyer
Andrew H. Smith
Dr. Raj Yavatkar
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)