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