COPS Usage for Policy Provisioning (COPS-PR)
RFC 3084
Document | Type |
RFC - Historic
(March 2001; No errata)
Status changed by status-change-copspr-sppi-to-historic
Was draft-ietf-rap-pr (rap WG)
|
|
---|---|---|---|
Last updated | 2016-04-28 | ||
Stream | IETF | ||
Formats | plain text pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 3084 (Historic) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
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)......................21 4.5. PRC Class Provisioning Error Object (CPERR)...................22 4.6. Error PRID Object (ErrorPRID).................................23 5. COPS-PR Client-Specific Data Formats............................23 5.1. Named Decision Data...........................................23 5.2. ClientSI Request Data.........................................24 5.3. Policy Provisioning Report Data...............................24 5.3.1. Success and Failure Report-Type Data Format.................24 5.3.2. Accounting Report-Type Data Format..........................25 6. Common Operation................................................26 7. Fault Tolerance.................................................28 8. Security Considerations.........................................29 9. IANA Considerations.............................................29 10. Acknowledgements...............................................30Show full document text