Common Open Policy Service
From Seo Wiki - Search Engine Optimization and Programming Languages
|This article's citation style may be unclear. The references used may be made clearer with a different or consistent style of citation, footnoting, or external linking. (September 2009)|
The Common Open Policy Service (COPS) Protocol is part of the internet protocol suite as defined by the IETF's RFC 2748. COPS specifies a simple client/server model for supporting policy control over Quality of Service (QoS) signaling protocols (e.g. RSVP). Policies are stored on servers, also known as Policy Decision Points (PDP), and are enforced on clients, also known as Policy Enforcement Points (PEP). There are two models of COPS: The Outsourcing Model and the Provisioning Model, considered from the view of the client or PEP.
The Outsourcing Model is the simplest COPS implementation. In this model, all policies are stored at the PDP. Whenever the PEP needs to make a decision, it sends all relevant information to the PDP. The PDP analyzes the information, makes the decision, and relays it to the PEP. The PEP then simply enforces the decision.
In the Provisioning Model, see RFC 3084 COPS Usage for Policy Provisioning (COPS-PR), the PEP reports its decision-making capabilities to the PDP. The PDP then downloads relevant policies on to the PEP. The PEP can then make its own decisions based on these policies. The Provisioning Model uses the Policy Information Base as a repository of the policies.
The COPS-MAID Internet Draft introduces QoS extensions to the protocol for Multi-Access environment.
See  for links to some COPS implementations.
|File:Crystal Clear app browser.png||This World Wide Web-related article is a stub. You can help Wikipedia by expanding it.|