References from rfc7986

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-daboo-icalendar-extensions New Properties for iCalendar
Refs Ref'd by
informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 2397 The "data" URL scheme
Refs Ref'd by
Proposed Standard informatively references
RFC 3261 SIP: Session Initiation Protocol
Refs Ref'd by
Proposed Standard informatively references
RFC 3966 The tel URI for Telephone Numbers
Refs Ref'd by
Proposed Standard informatively references
RFC 4122 A Universally Unique IDentifier (UUID) URN Namespace
Refs Ref'd by
Proposed Standard normatively references
RFC 5122 Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)
Refs Ref'd by
Proposed Standard informatively references
RFC 5234 Augmented BNF for Syntax Specifications: ABNF
Refs Ref'd by
Internet Standard normatively references
RFC 5545 Internet Calendaring and Scheduling Core Object Specification (iCalendar)
Refs Ref'd by
Proposed Standard informatively references
RFC 5546 iCalendar Transport-Independent Interoperability Protocol (iTIP)
Refs Ref'd by
Proposed Standard normatively references
RFC 7230 Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
Refs Ref'd by
Proposed Standard informatively references
STD 68 Augmented BNF for Syntax Specifications: ABNF
Refs Ref'd by
Internet Standard normatively references