Location Information Server (LIS) Discovery Using IP Addresses and Reverse DNS
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: RFC Editor <firstname.lastname@example.org>, geopriv mailing list <email@example.com>, geopriv chair <firstname.lastname@example.org> Subject: Protocol Action: 'Location Information Server (LIS) Discovery using IP address and Reverse DNS' to Proposed Standard (draft-ietf-geopriv-res-gw-lis-discovery-08.txt) The IESG has approved the following document: - 'Location Information Server (LIS) Discovery using IP address and Reverse DNS' (draft-ietf-geopriv-res-gw-lis-discovery-08.txt) as Proposed Standard This document is the product of the Geographic Location/Privacy Working Group. The IESG contact persons are Richard Barnes and Gonzalo Camarillo. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-geopriv-res-gw-lis-discovery/
Technical Summary: The residential gateway is a device that has become an integral part of home networking equipment. Discovering a Location Information Server (LIS) is a necessary part of acquiring location information for location-based services. However, discovering a LIS when a residential gateway is present poses a configuration challenge, requiring a method that is able to work around the obstacle presented by the gateway. This document describes a solution to this problem. The solution provides alternative domain names as input to the LIS discovery process based on the network addresses assigned to a Device. Working Group Summary: There is strong consensus around this document in the working group. It is required for the HELD protocol's discovery mechanism to work through NATs and other residential gateways. Document Quality: There are a few existing implementations of the protocol. It has been incorporated into several emerging standards, especially for emergency calling. The document received thorough review from the DNS community on its use of the reverse DNS. Personnel: The Document Shepherd is Alissa Cooper. The responsible Area Director is Richard Barnes. RFC Editor Note: At the end of Section 7: NEW: """ DNS queries that are not blocked as <xref target="RFC6303"/> demands, or directed to servers outside the network, can cause the addresses that are in use within the network to be exposed outside of the network. For resolvers within the network, implementing <xref target="RFC6303"/> avoids this issue; otherwise, the problem cannot be avoided without blocking DNS queries to external servers. """