RFC 1876:A Means for Expressing Location Informati...
RFC-Ref

RR


Click on the red underlined text to get to the source

... This memo defines a new DNS RR type for experimental purposes. This RFC describes a mechanism to allow the DNS ...
... This RFC defines the format of a new Resource Record (RR) for the Domain Name System (DNS ...


... ;; network LOC RR derived from ZIP data. note use of precision defaults cambridge-net.kei.com. LOC 42 21 54 N 71 06 18 W -24m 30m ...
... ;; higher-precision host LOC RR. note use of vertical precision default loiosh.kei.com. LOC 42 21 43.952 N 71 5 6.344 W ...


... Application use of the LOC RR ...
... Some uses for the LOC RR have already been suggested, including the USENET backbone ...
... IP packet, and network management applications that could use LOC RRs to generate a map of hosts and routers ...
... less precise or larger area when a host does not have an associated LOC RR, it MAY support use of the algorithm in section 5.2.3, as noted in sections 5.2.1 and 5.2.2. If fallback is desired, this ...
... specify the location of a network or subnet without requiring LOC RR data for each individual host. For example, a computer lab with 24 ...
... workstations, all of which are on the same subnet and in basically the same location, would only need a LOC RR for the subnet. (However, if the file server's location has been more precisely ...
... subnet. (However, if the file server's location has been more precisely measured, a separate LOC RR for it can be placed in the DNS.) ...
... backbone flow maps do), it MUST check for a LOC RR associated with that name. (CNAME records should be followed as for any other RR ...
... RR associated with that name. (CNAME records should be followed as for any other RR type.) ...
... If there is no LOC RR for that name, all A records (if any) associated with the name MAY be checked for network ...
... network (or subnet) LOC RRs using the "Searching by Network or Subnet" algorithm ...
... network or subnet LOC RRs, the application may choose to use any, some, or all of the LOC RRs found, possibly in combination. It is suggested that multi-homed hosts ...
... RRs, the application may choose to use any, some, or all of the LOC RRs found, possibly in combination. It is suggested that multi-homed hosts have LOC RRs for their name in the DNS ...
... RRs found, possibly in combination. It is suggested that multi-homed hosts have LOC RRs for their name in the DNS to avoid any ambiguity in these cases. ...
... domain names that do not have associated A records must have a LOC RR associated with their name in order for location information to be accessible. ...
... namespace (see[RFC 1034], section 5.2.1), then check for a LOC RR associated with that name. ...
... If there is no LOC RR for the name, the address MAY be checked for network ...
... network (or subnet) LOC RRs using the "Searching by Network or Subnet ...
... Even if a host's name does not have any associated LOC RRs, the network(s) or subnet ...
... followed to find a network or subnet LOC RR associated with the IP address. This algorithm is adapted slightly from that specified in ...
... Since subnet LOC RRs are (if present) more specific than network LOC RRs ...
... RRs are (if present) more specific than network LOC RRs, it is best to use them if available. In order to do so, we build a stack of network and subnet ...
... [RFC 1101] search, then work our way down the stack until a LOC RR is found. ...
... Push the name "isi-net.isi.edu" onto the stack of names to be searched for LOC RRs later. 3. Since an A RR ...
... RRs later. 3. Since an A RR was found, repeat using mask from RR (255.255.255.0), constructing a query ...
... 3. Since an A RR was found, repeat using mask from RR (255.255.255.0), constructing a query for 0.2.9.128.IN-ADDR.ARPA ...
... Push the name "div2-subnet.isi.edu" onto the stack of names to be searched for LOC RRs later. 4. Since another A RR ...
... RRs later. 4. Since another A RR was found, repeat using mask 255.255.255.240 (x'FFFFFFF0'), constructing a query for 16.2.9.128.IN-ADDR.ARPA ...
... Push the name "inc-subsubnet.isi.edu" onto the stack of names to be searched for LOC RRs later. 5. Since no A RR ...
... RRs later. 5. Since no A RR is present at 16.2.9.128.IN-ADDR.ARPA., there are no more subnet ...
... subnet levels to search. We now pop the top name from the stack and check for an associated LOC RR. Repeat until a LOC RR is found. ...
... search. We now pop the top name from the stack and check for an associated LOC RR. Repeat until a LOC RR is found. ...
... In this case, assume that inc-subsubnet.isi.edu does not have an associated LOC RR, but that div2-subnet.isi.edu does. We will then use div2-subnet ...
... subnet.isi.edu does. We will then use div2-subnet.isi.edu's LOC RR as an approximation of this host's location. (Note that even if isi-net.isi.edu has a LOC RR ...
... RR as an approximation of this host's location. (Note that even if isi-net.isi.edu has a LOC RR, it will not be used if a subnet also has a LOC RR ...
... RR, it will not be used if a subnet also has a LOC RR.) ...
... The LOC record is defined for all RR classes, and may be used with non-IN ...


... High-precision LOC RR information could be used to plan a penetration of physical security ...
... method to potential attackers, we declined the opportunity to name this RR "ICBM". ...


... /* * routines to convert between on-the-wire RR format and zone file * format. Does not contain conversion to/from decimal degrees; * divide or multiply by 60*60*1000 for that. ...
... PUTLONG(alt,bcp); return (16); /* size of RR in octets */ } ...
... } /* takes an on-the-wire LOC RR and prints it in zone file * (human readable) format. */ char * ...
... if (versionval) { sprintf(cp,"; error: unknown LOC RR version"); return (cp); ...



Google
Web
RFC-Ref