References from draft-ietf-geopriv-flow-identity
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 160 |
References Referenced by |
informatively references | ||
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 | normatively references | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
RFC 4340 |
Datagram Congestion Control Protocol (DCCP)
References Referenced by |
Proposed Standard | informatively references | |
RFC 4960 |
Stream Control Transmission Protocol
References Referenced by |
Proposed Standard | informatively references | |
RFC 5741 |
RFC Streams, Headers, and Boilerplates
References Referenced by |
Informational | Possible Reference | Possible Downref |
RFC 5985 |
HTTP-Enabled Location Delivery (HELD)
References Referenced by |
Proposed Standard | normatively references | |
RFC 6155 |
Use of Device Identity in HTTP-Enabled Location Delivery (HELD)
References Referenced by |
Proposed Standard | normatively references | |
RFC 6280 |
An Architecture for Location and Location Privacy in Internet Applications
References Referenced by |
Best Current Practice | informatively references | |
RFC 768 |
User Datagram Protocol
References Referenced by |
Internet Standard | informatively references | |
RFC 793 |
Transmission Control Protocol
References Referenced by |
Internet Standard | informatively references | |
STD 66 |
References Referenced by |
normatively references |