References to RFC 5986
These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| RFC 6881 |
Best Current Practice for Communications Services in Support of Emergency Calling
References Referenced by |
Best Current Practice | normatively references | |
| RFC 7105 |
Using Device-Provided Location-Related Measurements in Location Configuration Protocols
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7216 |
Location Information Server (LIS) Discovery Using IP Addresses and Reverse DNS
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7286 |
Application-Layer Traffic Optimization (ALTO) Server Discovery
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8155 |
Traversal Using Relays around NAT (TURN) Server Auto Discovery
References Referenced by |
Proposed Standard | normatively references | |
| draft-ietf-add-split-horizon-authority |
Establishing Local DNS Authority in Validated Split-Horizon Environments
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5985 |
HTTP-Enabled Location Delivery (HELD)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6443 |
Framework for Emergency Calling Using Internet Multimedia
References Referenced by |
Informational | informatively references | |
| RFC 7227 |
Guidelines for Creating New DHCPv6 Options
References Referenced by |
Best Current Practice | informatively references | |
| RFC 7840 |
A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) Protocol
References Referenced by |
Proposed Standard | informatively references |