白名单，绑定列表和解析列表如何工作的

你好，
我试图理解这些清单是如何工作的。拜托，让我做一些修改，如果他们错了就改正。
首先，我开始使用白名单来过滤试图连接到我的外围设备的中心地址。我手动管理这个白名单，直到出现BLE 4.2和隐私1.2。在这里，我们有RPA或随机地址，现在，试图连接到我的外设的相同设备有不同的BD地址从一个连接到下一个。我们不能使用白名单更长的设备连接过滤。
所以，我开始使用绑定地址列表。绑定需要配对，并且配对在连接之后不是强制的。配对是加密连接和密钥交换所必需的。我的意思是，绑定过程将节省BDA到债券清单和密钥来解决列表。这些密钥是我们需要从中央解析随机地址并能够再次加密连接，而不是管理连接本身。我的意思是，任何中央设备（保税或无保税）将连接到我的外围设备。只有粘接设备才能获得成功的认证。别人，不会得到认证，但他们可以保持连接和未经验证的如果不应。配对和认证可以要求从中央以及周边。
我一直在测试不同的东西，我看到了以下几点：
当配对过程完成后，它会自动包括在周围的白名单中的BDA。最多可保存8个地址。第九个将不会被保存。如果中央的地址是随机型和改变每一个连接，每一个新的地址将被列入白名单的新指标。
当配对过程完成后，它会自动包括在周围的键列表中央的BDA。如果中央的BDA是RPA型和改变每一个连接，在列表上随机地址将被新的更新。
我还没有测试解决方案列表。是否有任何文件，所有的清单管理机制的描述？
如有任何修改或澄清，我将不胜感激。
最好的问候，
阿斯尔·纽曼。



     以下为原文
  Hello,

I'm trying to understand how all these lists work. Please, let me do some afirmations and correct them if they are wrong.

Firstly, I started working with whitelist to filter address of centrals that were trying to connect to my peripheral device. I managed this whitelist manually and it worked fine until appears ble 4.2 and its privacy 1.2. Here we have RPA or random address and now, the same device that is trying to connect to my peripheral has different BD address from one connection to next one. We can not employe whitelist longer for device connection filtering.

So, I started working with bonded addresses list. Bonding requires pairing, and pairing is not mandatory after a connection is stablished. Pairing is necessary for encrypt a connection and for keys exchange. I mean that bonding process will save BDA to bond list and keys to resolve list. These keys are which we will need to resolve random address from central and to be able to encrypt connection again, but not to manage the connection itself. I mean, any central device (bonded or unbonded) will get to connect to my peripheral. Only bonded devices will get authenticate succesfuly. Others, will not get authentication but they could stay connected and unauthenticated if it is not requiered. Pairing and authentication can be requested from central as well as from peripheral.

I've been testing diferent things and I've seen followings:
- When Pairing process is completed it automatically includes the central's BDA in the peripheral's whitelist. Up to 8 address can be saved. The 9th one will not be saved. If central's address is random type and it changes every connection, each new address will be included as new index in the whitelist.
- When Pairing process is completed it automatically includes the central's BDA in the peripheral's bond list. If central's BDA is RPA type and change every connection, the previous random address in the list will be updated with the new one.

I've not tested resolve list yet. Is there any document in which all that list management mechanism is described ?

Any correction/clarification of my text will be appreciated.

Best regards,
Asier.