@deebeeeff 

No, from a routing perspective, there is no real downside.  The only thing you might run into is when a client for example an iOS or Android device has a private address enabled.  This option breaks features in a router that are MAC address based.  If you plan to use Reserved addresses we would recommend disabling that private address feature  

  @Carl 

Thanks for the reply.

I am feeling a little dense here. When you are saying private address, do you mean a static IP set by the device?

Thanks,

Dave

  @deebeeeff 

So every device has a MAC address, which stands for media access control address.  A shorthand of this is it can sometimes be called Physical Address or in iOS its called Wi-Fi Address.  A little over a year ago Apple and Android added an option to make this address "private" or commonly known as "spoofed"  This feature works similarly to how a VPN masks your identity.  This feature masks the identity of your device.  The problem is that the feature has consequences to network features, like parental controls, and reserved addresses that rely on this address to function.  Each time these devices reconnect to the network, this spoofed address can change making features like Parental Conrols and Address reservations impossible to use.  

I know that was long but did it help?

  @Carl 

Yeah, that makes sense. 

I appreciate the info.

I'll probably just leave the reserved addresses alone except for the ones I have already done.

Thanks,

Dave