Editing Delegated Path Validation (section)

=== Relaying, re-direction and multicasting ===
[[File:Delegated path validation.png|thumb|upright=1.7|Application of the DPV framework in [[Transport Layer Security|TLS]]-based communications, with the optional use of a relaying mechanism by the primary DPV server.]]
In certain network environments, particularly those with [[Firewall (computing)|firewalls]], a DPV server may encounter difficulties in obtaining all the necessary information to process a validation request. To address this, a DPV server can be configured to leverage the services of other DPV servers. In such scenarios, the client remains unaware that the primary DPV server is utilizing additional servers to fulfill the request. Essentially, the primary DPV server acts as a client to another DPV server, facilitating a more comprehensive validation process. Unlike end clients, DPV servers typically have more substantial computing and memory resources, enabling them to employ relaying, re-direction, or [[multicast|multicasting mechanisms]].<ref name=RFC3379 />

The protocols designed to support these operations may include optional fields and extensions to facilitate relaying, re-direction, or multicasting between DPV servers. However, it is not expected that DPV clients will support these features. If a protocol incorporates such functionalities, it must also provide mechanisms to ensure compatibility with DPV clients and servers that do not support these advanced features, ensuring adherence to the basic protocol requirements.<ref name=RFC3379 />