References from rfc6753

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
BCP 160 An Architecture for Location and Location Privacy in Internet Applications
Refs Ref'd by
Best Current Practice 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 informatively references
RFC 2818 HTTP Over TLS
Refs Ref'd by
Informational informatively references
RFC 3261 SIP: Session Initiation Protocol
Refs Ref'd by
Proposed Standard informatively 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 4745 Common Policy: A Document Format for Expressing Privacy Preferences
Refs Ref'd by
Proposed Standard informatively references
RFC 4825 The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
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 informatively references
RFC 5491 GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations
Refs Ref'd by
Proposed Standard informatively references
RFC 5687 GEOPRIV Layer 7 Location Configuration Protocol: Problem Statement and Requirements
Refs Ref'd by
Informational informatively references
RFC 5741 RFC Streams, Headers, and Boilerplates
Refs Ref'd by
Informational Possible Reference Possible Downref
RFC 5751 Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification
Refs Ref'd by
Proposed Standard 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 informatively references
RFC 6125 Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)
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 6280 An Architecture for Location and Location Privacy in Internet Applications
Refs Ref'd by
Best Current Practice informatively references
RFC 6442 Location Conveyance for the Session Initiation Protocol
Refs Ref'd by
Proposed Standard informatively references