COPS Server Test Suite Data Sheet
Test Suite:
COPS Server Test Suite
Direction:
Server

The Common Open Policy Service (COPS) Protocol is 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). The server side acts as Policy Decision Points (PDP), storing the policies. The client, also known as Policy Enforcement Points (PEP), enforces the policies when external event happened. 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 Server Test Suite has been designed to act as a malicious PEP which sends exceptional requests in COPS protocol layers to the tested entity.

Used specifications

Specification
Title
RFC2748

The COPS (Common Open Policy Service) Protocol

RFC3084

COPS Usage for Policy Provisioning (COPS-PR)

RFC2749

COPS usage for RSVP

Tool-specific information

Tested messages
Specifications
COPS Client Open Message

RFC2748

COPS Client Close Message

RFC2748

COPS Keep Alive Message

RFC2748

COPS Request Message

RFC2748, RFC3084, RFC2749

COPS Report Message

RFC2748, RFC3084, RFC2749

COPS Delete Request Message

RFC2748, RFC2749

Test tool general features
  • Fully automated black-box negative testing
  • Ready-made test cases
  • Written in Java(tm)
  • GUI command line remote interface modes
  • Instrumentation (health-check) capability
  • Support and maintenance
  • Comprehensive user documentation
  • Results reporting and analysis