core: Consider moving whitelist/blacklist properties to debug section.

openthread / spinel-spec

Spinel Specification: a general management protocol for enabling a host device to communicate with and manage a Network Control Processor (NCP).

BSD 3-Clause "New" or "Revised" License

3 stars 5 forks source link

core: Consider moving whitelist/blacklist properties to debug section. #5

Open darconeous opened 7 years ago

darconeous commented 7 years ago

I'm considering moving the following properties (related to whitelist/blacklist) to the debug section:

PROP_MAC_WHITELIST
PROP_MAC_WHITELIST_ENABLED
PROP_MAC_BLACKLIST
PROP_MAC_BLACKLIST_ENABLED

The reason I'm considering moving them is that they aren't used as a normal part of the operation of the MAC.

Thoughts?

abtink commented 7 years ago

These properties can be used beyond debugging/testing and are currently used in certain scenarios (e.g., to ensure a new device stays with same parent/assisting device - initial joining/pairing).

darconeous commented 7 years ago

But is that really the right solution to the problem trying to be addressed? Sounds more like a hack.

abtink commented 7 years ago

We need a (probably new) mechanism for such situations (e.g., to ensure a device attached to a particular parent during pairing after it does the insecure connection). I agree whitelist/blacklist may not be the ideal approach but that's the currently supported way.