References from rfc7378

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 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 informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice informatively references
RFC 2818 HTTP Over TLS
Refs Ref'd by
Informational informatively references
RFC 3693 Geopriv Requirements
Refs Ref'd by
Informational informatively references
RFC 3694 Threat Analysis of the Geopriv Protocol
Refs Ref'd by
Informational informatively references
RFC 3748 Extensible Authentication Protocol (EAP)
Refs Ref'd by
Proposed Standard informatively references
RFC 3863 Presence Information Data Format (PIDF)
Refs Ref'd by
Proposed Standard informatively references
RFC 4474 Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)
Refs Ref'd by
Proposed Standard informatively references
RFC 4479 A Data Model for Presence
Refs Ref'd by
Proposed Standard informatively references
RFC 4740 Diameter Session Initiation Protocol (SIP) Application
Refs Ref'd by
Proposed Standard informatively references
RFC 5069 Security Threats and Requirements for Emergency Call Marking and Mapping
Refs Ref'd by
Informational 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 5582 Location-to-URL Mapping Architecture and Framework
Refs Ref'd by
Informational informatively references
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 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
RFC 6444 Location Hiding: Problem Statement and Requirements
Refs Ref'd by
Informational informatively references
RFC 6753 A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)
Refs Ref'd by
Proposed Standard informatively references