Quoting Mike Taylor <[log in to unmask]>:
> With my Stern Academic's hat on, I agree. With my Need To Get Stuff
> Done hat on, I don't. We both know that the purity of the ZeeRex
> record as a service-description-and-nothing-else is already hopelessly
But more information in the ServerInfo such as "name" is service description.
What we are "missing", I think, is the ability to describe the server. This
used to be a feature of DNS but long "depreciated" (like finger) due to antics
of the nasty parasitic elements that have overwhelmed our public networks.
Right now I'd use IP maps (there are some excellent ones around), DNS (probably
closed to outsiders but it does not hurt to try) and Whois to create ones own
mapping metadata and segmentation of the targets into country of origin and
type. Even with the data potentially available via a server supplied record
the chances that such info is provided is less than certain.. I'd extend
ServerInfo in a local database and fill in the missing Info with "best guesses".
Given the rather limited number of targets the effort to clean up things by
hand is minimal.
> compromised by not just a few but many of the included fields. The
> ones I am describing here are entirely analogous to (for example) the
> databaseInfo section's description, author, extent, etc.
As an aside:
I think its not irrelevant since a target with maps and sat. images covering
objects on the Greek-Albanian border could be quite different housed in a
server in Greece than from on a server in Italy.