Optional Key storage

[unknownconstant]

The developer should not need to implement storage and retrieval of IRK and LTK values for MAC addresses. The library should work out of the box without callbacks being defined for the storage and retrieval functions.

Not storing IRK & LTK means that devices will be paired but not bonded so the pairing Authreq value needs updating to reflect this so that centrals do not store LTK / IRK values and cause reconnection issues.

[unknownconstant]

I tried modifying the authreq / iocap parameters but the behaviour I've seen is that android expects the bonding process to complete regardless.

You suggested on the orignal thread that it could store IRK/LTK/MACs in ram as a default option - this could be implemented by having default storage/retreival callbacks which are overriden if the developer wants to. The merge above rejects unknown LTKs & will function without storage of keys until a device attempts to reconnect.