Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
The original purpose of IP addresses is to provide a physical unique identification for delivery of packets. To allow scalability, the IP address is split into a network number and a host number. To allow even larger scalability, network numbers are aggregated, sharing the same binary prefix, to reduce routing table sizes. Both networks and aggregated networks are generally tied to the physical topology.
In addition to using IP addressing to deliver packets on networks, network numbers have often been used for some type of access control. The latter is what causes problems when an IP address that's more or less required to represent some location in the physical topology is also used for some kind of role control. E.g. network 5 contains our servers, network 6 contains sales agents, or network 50 for data and network 51 for VoIP.
With laptops, user roles can't as easily be tied to a network number, and likewise, be used for something like a software based VoIP phone on a PC.
Consider using IP addressing just for L3 topology purposes, and some other method for role/use identification. I would suggest you discard your 3 options and think "outside the box". How might you "identify" data, VoIP and/or video without using IP addressing?
