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

[darconeous]

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]

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]

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

[abtink]

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.