Comment 1 for bug 1526203

AFAIK, most work should be done on library side. It's almost clear (and does not seem to be a challenge) on API/UI side (but requires a couple of days for implementation still).

Changes on API side:
1. restrictions validation change so that Public and Floating are treated as separate networks.
2. probably both old (Floating inside Public) and new (Floating has no intersection with Public) models can be used by user's choice.