RFC 7216: Location Information Server (LIS) Discovery Using IP Addresses and Reverse DNS
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7216
- Published
- April 2014
- Authors
- M. Thomson; R. Bellis
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7105Using Device-Provided Location-Related Measurements in Location Configuration ProtocolsCurrent
January 2014
- RFC 6915Flow Identity Extension for HTTP-Enabled Location Delivery (HELD)Current
April 2013
- RFC 6753A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)Current
October 2012
- RFC 5768Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP)Current
April 2010
- RFC 5627Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)Current
October 2009
- RFC 3257Stream Control Transmission Protocol Applicability StatementCurrent
April 2002
- RFC 7383Internet Key Exchange Protocol Version 2 (IKEv2) Message FragmentationCurrent
November 2014
- RFC 6967Analysis of Potential Solutions for Revealing a Host Identifier (HOST_ID) in Shared Address DeploymentsCurrent
June 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?