Correct behavior with respect to dynamic password change should be defined

It is possible to re-configure TCPMD5 password for a client during ODL runtime using restconf. See the last URL/data in https://wiki.opendaylight.org/view/BGP_LS_PCEP:TCP_MD5_Guide#PCEP_2

Implementation in Lithium works fine with this dynamic password re-configuration only up to the moment session is established. But the behavior when password is re-configured while session is established is not very secure.

For example, session is not terminated when passwords no longer match.
Another example: After deleting password element, PCC is still able to reconnect using its password.
Note that these examples are not strictly bugs, as there is no documentation on which behavior should be expected.

Thus it would be nice to define the desired behavior for Beryllium.