1.. _bluetooth_mesh_srpl_srv:
2
3Solicitation PDU RPL Configuration Server
4#########################################
5
6The Solicitation PDU RPL Configuration Server model is a foundation model defined by the Bluetooth
7mesh specification. The model is enabled if the node has the :ref:`bluetooth_mesh_od_srv` enabled.
8
9The Solicitation PDU RPL Configuration Server model was introduced in the Bluetooth Mesh Protocol
10Specification version 1.1, and manages the Solicitation Replay Protection List (SRPL) saved on the
11device. The SRPL is used to reject Solicitation PDUs that are already processed by a node. When a
12valid Solicitation PDU message is successfully processed by a node, the SSRC field and SSEQ field
13of the message are stored in the node's SRPL.
14
15The Solicitation PDU RPL Configuration Server does not have an API of its own, and relies on a
16:ref:`bluetooth_mesh_srpl_cli` to control it. The model only accepts messages encrypted with an
17application key as configured by the Configuration Client.
18
19If present, the Solicitation PDU RPL Configuration Server model must only be instantiated on the
20primary element.
21
22Configurations
23**************
24
25For the Solicitation PDU RPL Configuration Server model, the
26:kconfig:option:`CONFIG_BT_MESH_PROXY_SRPL_SIZE` option can be configured to set the size of the
27SRPL.
28
29API reference
30*************
31
32.. doxygengroup:: bt_mesh_sol_pdu_rpl_srv
33   :project: Zephyr
34   :members:
35