References from draft-thomson-geopriv-relative-location
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 | ||
| BCP 26 |
References Referenced by |
normatively references | ||
| draft-ietf-httpbis-p3-payload |
HTTP/1.1, part 3: Message Payload and Content Negotiation
References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3688 |
The IETF XML Registry
References Referenced by |
Best Current Practice | informatively references | |
| RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | informatively references | |
| RFC 4119 |
A Presence-based GEOPRIV Location Object Format
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4776 |
Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5139 |
Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
| RFC 5491 |
GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations
References Referenced by |
Proposed Standard | normatively references | |
| STD 66 |
References Referenced by |
informatively references |