References from RFC 7946
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 13 |
References Referenced by |
normatively references | ||
| 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 5870 |
A Uniform Resource Identifier for Geographic Locations ('geo' URI)
References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 6772 |
Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6838 |
Media Type Specifications and Registration Procedures
References Referenced by |
Best Current Practice | normatively references | |
| RFC 7159 |
The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7464 |
JavaScript Object Notation (JSON) Text Sequences
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7493 |
The I-JSON Message Format
References Referenced by |
Proposed Standard | informatively references |