Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

COPS Usage for Policy Provisioning (COPS-PR) (RFC3084)

IP.com Disclosure Number: IPCOM000005278D
Original Publication Date: 2001-Mar-01
Included in the Prior Art Database: 2001-Aug-20
Document File: 35 page(s) / 79K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

K. Chan: AUTHOR [+9]

Abstract

This document describes the use of the Common Open Policy Service (COPS) protocol for support of policy provisioning (COPS-PR). This specification is independent of the type of policy being provisioned (QoS, Security, etc.) but focuses on the mechanisms and conventions used to communicate provisioned information between PDPs and PEPs. The protocol extensions described in this document do not make any assumptions about the policy data model being communicated, but describe the message formats and objects that carry the modeled policy data.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 4% of the total text.

Network Working Group K. Chan Request for Comments: 3084 J. Seligson Category: Standards Track Nortel Networks D. Durham

Intel

S. Gai K. McCloghrie

Cisco S. Herzog

IPHighway F. Reichmeyer

PFN R. Yavatkar

Intel

A. Smith Allegro Networks

March 2001

COPS Usage for Policy Provisioning (COPS-PR)

Status of this Memo

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.

Copyright Notice

Copyright (C) The Internet Society (2001). All Rights Reserved.

Abstract

This document describes the use of the Common Open Policy Service (COPS) protocol for support of policy provisioning (COPS-PR). This specification is independent of the type of policy being provisioned (QoS, Security, etc.) but focuses on the mechanisms and conventions used to communicate provisioned information between PDPs and PEPs. The protocol extensions described in this document do not make any assumptions about the policy data model being communicated, but describe the message formats and objects that carry the modeled policy data.

Chan, et al. Standards Track [Page 1]

RFC 3084 COPS-PR March 2001

Conventions used in this document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC-2119].

Table of Contents

Glossary........................................................... 3 1. Introduction.................................................... 3 1.1. Why COPS for Provisioning?.................................... 5 1.2. Interaction between the PEP and PDP........................... 5 2. Policy Information Base (PIB)................................... 6 2.1. Rules for Modifying and Extending PIBs........................ 7 2.2. Adding PRCs to, or deprecating from, a PIB.................... 7 2.2.1. Adding or Deprecating Attributes of a BER Encoded PRC....... 8 2.3. COPS Operations Supported for a Provisioning Instance......... 8 3. Message Content................................................. 9 3.1. Request (REQ) PEP PDP..................................... 9 3.2. Decision (DEC) PDP PEP....................................10 3.3. Report State (RPT) PEP PDP................................12 4. COPS-PR Protocol Objects........................................13 4.1. Complete Provisioning Instance Identifier (PRID)..............14 4.2. Prefix PRID (PPRID)...........................................15 4.3. Encoded Provisioning Instance Data (EPD)......................16 4.4. Global Provisioning Error Object (GPERR).................