PCC/PCE MD5 Key

A stateful Path Computation Element (PCE) server automates the creation of traffic engineering paths across the network, increasing network utilization and enabling a customized programmable networking experience with the use of Path Computation Element Protocol (PCEP) communication with a Path Computation Client (PCC). A PCC sends LSP reports to a PCE server, and the PCE updates or provisions LSPs back to the PCC. The data sent over a PCEP session is crucial for a PCE server to perform external path computing. As a result, an attack on the PCEP communication can disrupt network services. If altered PCEP messages are sent to a PCC, inappropriate LSPs can be set up. Similarly, if altered PCEP messages are sent to a PCE, an incorrect view of the network is learned by the PCE. Considering the significance of the PCEP communication between a PCE and PCC in executing the PCE functionalities effectively, the PCEP session should be secured using TCP-MD5 authentication in accordance with RFC 5440. MD5 protects the communication between a PCE and PCC over a PCEP session, which might be subject to an attack and thus can disrupt network services. This feature introduces PCEP session protection through the MD5 authentication key.