References from rfc7199

This is an experimental product. 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.

Reference type help

Document Title Status Type Downref
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
draft-ietf-geopriv-deref-protocol A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)
Refs Ref'd by
Proposed Standard informatively references
draft-ietf-geopriv-dhcp-lbyr-uri-option Dynamic Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a Location Uniform Resource Identifier (URI)
Refs Ref'd by
Proposed Standard normatively references
draft-ietf-geopriv-policy Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information
Refs Ref'd by
Proposed Standard informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1
Refs Ref'd by
Draft Standard normatively references
RFC 2617 HTTP Authentication: Basic and Digest Access Authentication
Refs Ref'd by
Draft Standard normatively references
RFC 2818 HTTP Over TLS
Refs Ref'd by
Informational normatively references Downref
RFC 3234 Middleboxes: Taxonomy and Issues
Refs Ref'd by
Informational informatively references
RFC 3688 The IETF XML Registry
Refs Ref'd by
Best Current Practice normatively references
RFC 3693 Geopriv Requirements
Refs Ref'd by
Informational informatively references
RFC 4119 A Presence-based GEOPRIV Location Object Format
Refs Ref'd by
Proposed Standard informatively references
RFC 4648 The Base16, Base32, and Base64 Data Encodings
Refs Ref'd by
Proposed Standard informatively references
RFC 4745 Common Policy: A Document Format for Expressing Privacy Preferences
Refs Ref'd by
Proposed Standard normatively references
RFC 4825 The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
Refs Ref'd by
Proposed Standard informatively references
RFC 4918 HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)
Refs Ref'd by
Proposed Standard informatively references
RFC 5246 The Transport Layer Security (TLS) Protocol Version 1.2
Refs Ref'd by
Proposed Standard normatively references
RFC 5606 Implications of 'retransmission-allowed' for SIP Location Conveyance
Refs Ref'd by
Informational informatively references
RFC 5687 GEOPRIV Layer 7 Location Configuration Protocol: Problem Statement and Requirements
Refs Ref'd by
Informational informatively references
RFC 5808 Requirements for a Location-by-Reference Mechanism
Refs Ref'd by
Informational informatively references
RFC 5985 HTTP-Enabled Location Delivery (HELD)
Refs Ref'd by
Proposed Standard normatively references
RFC 6155 Use of Device Identity in HTTP-Enabled Location Delivery (HELD)
Refs Ref'd by
Proposed Standard informatively references
RFC 6225 Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration Information
Refs Ref'd by
Proposed Standard informatively references