Juniper JUNOSE 11.1.X - BROADBAND ACCESS CONFIGURATION GUIDE 6-4-2010 Configuration Manual page 135

The JUNOSe Software COPS-PR implementation uses the outsourcing model that is
described in RFC 3084. In this model, the PEP delegates responsibility to the PDP
to make provisioning decisions on the PEP's behalf.
NOTE: When you upgrade from an earlier JUNOSe release, the software removes
the instance of SSCC that was configured with XDR.
If you are going to perform a unified ISSU from a JUNOSe release numbered lower
than Release 10.0.0 and you have an XDR configuration, unified ISSU is not supported
while an XDR configuration is presented.
The provisioning is event-driven and is based on policy requests rather than on an
action taken by an administrator the provisioning is initiated when the PDP receives
external requests and PEP events. Provisioning can be performed in bulk (for example,
an entire QoS configuration) or in smaller segments (for example, updating a marking
filter). The following list shows the interaction between the PEP and the PDP during
the COPS-PR operation.
Initial connection
1.
a. PEP starts the COPS-PR connection with the PDP.
b. PDP requests synchronization.
c. PEP sends all currently provisioned policies to PDP.
Change of interface state
2.
a. PEP requests provisioning of an interface from the PDP.
b. PDP determines policies and sends provisioning data to the PEP.
c. PEP provisions the policies.
PDP requests policy provisioning
3.
a. PDP determines new policies and sends provisioning data to the PEP.
b. PEP provisions the policies.
The information exchange between the PDP and PEP consists of data that is modeled
in Policy Information Bases (PIBs) and is encoded using the standard ASN.1 basic
encoding rules (BERs).
JUNOSe Software uses the following PIBs:
Chapter 1: Configuring Remote Access
Configuring the SRC Client
95