Static IP Client Issues

The Static IP Client node subtype was originally meant to be used for localtalk connected Macs with static IP address assignments handled by fastpaths. There were never very many of those and there probably aren't any now, so it's unclear exactly what network gizmo would actually be a Static IP Client.

To complicate matters even more, the address used by a Static IP Client has two names in NetDB III - one provided in the IP Connectivity Provider entry and the name of the Static IP Client itself. This is enough to make us ask if we really want to support Static IP Client, or if IP Connectivity Provider is a solution to the original problem.*

So for now, we'll pass on implementing Static IP Client in the front end, but allow for it in the data and middleware, just in case.

If Static IP Client is implemented we need to consider a couple of points:

  1. Does the user adding a Static IP Client have to have share an ownership group with the IP connectivity provider that owns the IP address? Probably.

  2. IP Connectivity Providers can't be removed from the database if they are servicing any Static IP Clients.