1.. _bluetooth_mesh_srpl_cli:
2
3Solicitation PDU RPL Configuration Client
4#########################################
5
6The Solicitation PDU RPL Configuration Client model is a foundation model defined by the Bluetooth
7mesh specification. The model is optional, and is enabled through the
8:kconfig:option:`CONFIG_BT_MESH_SOL_PDU_RPL_CLI` option.
9
10The Solicitation PDU RPL Configuration Client model was introduced in the Bluetooth Mesh Protocol
11Specification version 1.1, and supports the functionality of removing addresses from the
12solicitation replay protection list (SRPL) of a node that supports the
13:ref:`bluetooth_mesh_srpl_srv` model.
14
15The Solicitation PDU RPL Configuration Client model communicates with a Solicitation PDU RPL
16Configuration Server model using the application keys configured by the Configuration Client.
17
18If present, the Solicitation PDU RPL Configuration Client model must only be instantiated on the
19primary element.
20
21Configurations
22**************
23
24The Solicitation PDU RPL Configuration Client model behavior can be configured with the transmission
25timeout option :kconfig:option:`CONFIG_BT_MESH_SOL_PDU_RPL_CLI_TIMEOUT`. The
26:kconfig:option:`CONFIG_BT_MESH_SOL_PDU_RPL_CLI_TIMEOUT` controls how long the Solicitation PDU RPL
27Configuration Client waits for a response message to arrive in milliseconds. This value can be
28changed at runtime using :c:func:`bt_mesh_sol_pdu_rpl_cli_timeout_set`.
29
30API reference
31*************
32
33.. doxygengroup:: bt_mesh_sol_pdu_rpl_cli
34   :project: Zephyr
35   :members:
36