References from RFC 5582
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.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| BCP 14 |
References Referenced by |
normatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3528 |
Mesh-enhanced Service Location Protocol (mSLP)
References Referenced by |
Experimental | informatively references | |
| RFC 5012 |
Requirements for Emergency Context Resolution with Internet Technologies
References Referenced by |
Informational | informatively references | |
| RFC 5031 |
A Uniform Resource Name (URN) for Emergency and Other Well-Known Services
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5069 |
Security Threats and Requirements for Emergency Call Marking and Mapping
References Referenced by |
Informational | informatively references | |
| RFC 5222 |
LoST: A Location-to-Service Translation Protocol
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5223 |
Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5246 |
The Transport Layer Security (TLS) Protocol Version 1.2
References Referenced by |
Proposed Standard | informatively references |