LOC et.al. (what, no Ton'Loc?)

[bmanning@ISI.EDU]

> BTW, to all you folks who don't like LOC because it gives the physical
> location of your hardware, well strictly speaking that's your fault.  If
> you don't want your physical location to be known then either don't
> include a publicly query-able LOC record in your DNS, or else
> alternately just specify the location of the nearest branch office or
> whatever, or even just put the city's co-ordinates in there with a large
> enough size/precision field to encompass your POP, or whatever.
> 
> -- 
> 							Greg A. Woods

RFC 1876  already has a -very- cool method for injecting ambiguity.
>From the RFC:


SIZE         The diameter of a sphere enclosing the described entity, in
             centimeters, expressed as a pair of four-bit unsigned
             integers, each ranging from zero to nine, with the most
             significant four bits representing the base and the second
             number representing the power of ten by which to multiply
             the base.  This allows sizes from 0e0 (<1cm) to 9e9
             (90,000km) to be expressed.  This representation was chosen
             such that the hexadecimal representation can be read by
             eye; 0x15 = 1e5.  Four-bit values greater than 9 are
             undefined, as are values with a base of zero and a non-zero
             exponent.

             Since 20000000m (represented by the value 0x29) is greater
             than the equatorial diameter of the WGS 84 ellipsoid
             (12756274m), it is therefore suitable for use as a
             "worldwide" size.

You don't -have- to go to the nearest coordinate intersection for ambiguity.
....


-- 
--bill