RE: Proximity bonding

Frederic — Wed, 12 Mar 2014 08:52:51 GMT

Can someone help me here?

Frederic — Tue, 11 Mar 2014 11:06:32 GMT

some more questions:

I try to understand the whole paring/bonding procedure. In my use case I’m proximity peripheral.

If i configure the security parameters with no bonding, is than still a paring is done with short key encryption? If i configure the characteristic to require encryption but no MITM protection, than a paring is needed to encrypt data?
If i configure the security parameters with bonding then, the procedure is as in Figure 1 with the difference that long keys are exchanged and stored for fast reconnection next time? If bond is configured, is bonding then required or is it sufficient that the master perform a pairing?
If i have two displays with Yes/No entry, and I confirm that the two numbers are the same even though they are not, the connection is still established then?
If i configure the central and peripheral device as Keyboard only, then at both sides the same pin must be entered. Can i then store a fixed key on the peripheral side or is it still a random number?
If i configure no I/O capabilities the "just works" paring is done. How can I allow only certain devices to connect to my proximity peripheral device?
How can I ensure that not every proximity central device can connect to my proximity peripheral device? Is this only possible if i create a characteristic and handle it in application layer? For example: The central application must send a specific characteristic value after pairing else the connection is terminated?