10 The OpenDaylight controller provides an implementation of BGP
11 (Border Gateway Protocol), which is based on `RFC 4271 <https://tools.ietf.org/html/rfc4271>`_)
12 as a south-bound protocol plugin. The implementation renders all
13 basic *BGP speaker capabilities*, including:
15 Inter/Intra-AS peering
20 The plugin's **north-bound API** (``REST``/``Java``) provides to user:
22 * Fully dynamic run-time standardized BGP configuration
23 * Read-only access to all RIBs
24 * Read-write programmable RIBs
25 * Read-only reachability/link-state topology view
29 The OpenDaylight Path Computation Element Communication Protocol (PCEP)
30 plugin provides all basic service units necessary to build-up a
31 PCE-based controller. Defined by `RFC 8231 <https://tools.ietf.org/html/rfc8231>`_,
32 PCEP offers LSP management functionality for Active Stateful PCE, which is
33 the cornerstone for majority of PCE-enabled SDN solutions. It consists of
34 the following components:
37 * PCEP session handling
39 * Active Stateful PCE LSP Operations
42 Behavior/Feature Changes
43 ========================
44 ``pcep-topology-provider`` now allows PCEP capabilities, TLS configuration as well as PCEP
45 timer proposals to be configured on a per-topology basis rather than being global settings.
47 Rarely-used configuration knobs for PCEP ``auto-bandwidth`` and ``segment-routing`` extensions
48 have been migrated from the datastore to OSGi Configuration Admin properties.
57 No deprecated features.
61 The following table lists the issues resolved in this release.
63 .. jira_fixed_issues::
65 :versions: 0.19.0-0.19.3
69 The following table lists the known issues that exist in this release.
71 .. jira_known_issues::
73 :versions: 0.19.0-0.19.3