References from RFC 9073
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 |
|---|---|---|---|---|
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
| RFC 4589 |
Location Types Registry
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Internet Standard | normatively references | |
| RFC 5545 |
Internet Calendaring and Scheduling Core Object Specification (iCalendar)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5546 |
iCalendar Transport-Independent Interoperability Protocol (iTIP)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 6350 |
vCard Format Specification
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7986 |
New Properties for iCalendar
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8259 |
The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by |
Internet Standard | normatively references |