RFC 5986: Discovering the Local Location Information Server (LIS)

Discovery of the correct Location Information Server (LIS) in the local access network is necessary for Devices that wish to acquire location information from…

Read RFC 5986 on the RFC Editor

Outgoing relationships (19 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 1035: Domain names - implementation and specification
Normative reference — RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
Normative reference — RFC 3315: Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
Normative reference — RFC 4033: DNS Security Introduction and Requirements
Normative reference — RFC 2131: Dynamic Host Configuration Protocol
Normative reference — RFC 2818: HTTP Over TLS
Normative reference — RFC 2132: DHCP Options and BOOTP Vendor Extensions
Normative reference — RFC 4704: The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option
Normative reference — RFC 5985: HTTP-Enabled Location Delivery (HELD)
Normative reference — RFC 4848: Domain-Based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS)
Normative reference — RFC 4702: The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option
Informative reference — RFC 3118: Authentication for DHCP Messages
Informative reference — RFC 3693: Geopriv Requirements
Informative reference — RFC 3958: Domain-Based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS)
Informative reference — RFC 5222: LoST: A Location-to-Service Translation Protocol
Informative reference — RFC 5687: GEOPRIV Layer 7 Location Configuration Protocol: Problem Statement and Requirements
Informative reference — RFC 5808: Requirements for a Location-by-Reference Mechanism
Informative reference — RFC 5223: Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP)

Incoming relationships (6 related RFCs)

Normatively referenced by — RFC 5985: HTTP-Enabled Location Delivery (HELD)
Normatively referenced by — RFC 8155: Traversal Using Relays around NAT (TURN) Server Auto Discovery
Normatively referenced by — RFC 7216: Location Information Server (LIS) Discovery Using IP Addresses and Reverse DNS
Normatively referenced by — RFC 7105: Using Device-Provided Location-Related Measurements in Location Configuration Protocols
Informatively referenced by — RFC 7840: A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) Protocol
Informatively referenced by — RFC 9704: Establishing Local DNS Authority in Validated Split-Horizon Environments