References from rfc5546
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.
| 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 | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 2368 |
The mailto URL scheme Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 2446 |
iCalendar Transport-Independent Interoperability Protocol (iTIP) Scheduling Events, BusyTime, To-dos and Journal Entries Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 5545 |
Internet Calendaring and Scheduling Core Object Specification (iCalendar) Refs Ref'd by |
Proposed Standard | informatively references | |
| STD 1 |
Internet Official Protocol Standards Refs Ref'd by |
Historic | Possible Reference | Possible Downref |