no programmatic interface with *PolicyAdministration*, *PolicyExecution* or any other run-time ONAP components.
The diagram below shows a more detailed view of the architecture, as inspired by
-`RFC-2753 <https://tools.ietf.org/html/rfc2753>`__ and `RFC-3198 <https://tools.ietf.org/html/rfc3198>`__.
+`RFC-2753 https://tools.ietf.org/html/rfc2753` and `RFC-3198 https://tools.ietf.org/html/rfc3198`.
.. image:: images/PFDesignAndAdmin.svg
================ ============================== =======================================================================
**Service** **Endpoint** **Description**
================ ============================== =======================================================================
-PAP https://policy-pap The PAP service, used for policy administration and deployment. See
+PAP policy-pap The PAP service, used for policy administration and deployment. See
:ref:`Policy Design and Development <design-label>` for details of the
API for this service
-PDP-X-\ *domain* https://policy-pdpx-\ *domain* A PDP service is defined for each PDP group. A PDP group is identified
+PDP-X-\ *domain* policy-pdpx-\ *domain* A PDP service is defined for each PDP group. A PDP group is identified
by the domain on which it operates.
For example, there could be two PDP-X domains, one for admission
policies for ONAP proper and another for admission policies for VNFs of
operator *Supacom*. Two PDP-X services are defined:
- | https://policy-pdpx-onap
- | https://policy-pdpx-\ *supacom*
-PDP-D-\ *domain* https://policy-pdpd-\ *domain*
-PDP-A-\ *domain* https://policy-pdpa-\ *domain*
+ | policy-pdpx-onap
+ | policy-pdpx-\ *supacom*
+PDP-D-\ *domain* policy-pdpd-\ *domain*
+PDP-A-\ *domain* policy-pdpa-\ *domain*
================ ============================== =======================================================================
There is one and only one PAP service, which handles policy deployment, administration, and monitoring for all policies