References from draft-daviel-http-geo-header
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 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| BCP 78 |
Rights Contributors Provide to the IETF Trust
References Referenced by |
Best Current Practice | informatively references | |
| BCP 90 |
Registration Procedures for Message Header Fields
References Referenced by |
Best Current Practice | normatively references | |
| draft-daviel-html-geo-tag |
Geographic registration of HTML documents
References Referenced by |
Informational | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | normatively references | |
| RFC 2617 |
HTTP Authentication: Basic and Digest Access Authentication
References Referenced by |
Draft Standard | informatively references | |
| RFC 2731 |
Encoding Dublin Core Metadata in HTML
References Referenced by |
Informational | informatively references | |
| RFC 2965 |
HTTP State Management Mechanism
References Referenced by |
Historic | informatively references | |
| RFC 3693 |
Geopriv Requirements
References Referenced by |
Informational | informatively references | |
| RFC 3864 |
Registration Procedures for Message Header Fields
References Referenced by |
Best Current Practice | normatively references | |
| RFC 4346 |
The Transport Layer Security (TLS) Protocol Version 1.1
References Referenced by |
Historic | informatively references |