References from draft-mosko-icnrg-ccnxurischeme
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
References Referenced by |
Best Current Practice | normatively references | |
| BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references | |
| BCP 72 |
Guidelines for Writing RFC Text on Security Considerations
References Referenced by |
Best Current Practice | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3552 |
Guidelines for Writing RFC Text on Security Considerations
References Referenced by |
Best Current Practice | informatively references | |
| RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | informatively references | |
| RFC 3987 |
Internationalized Resource Identifiers (IRIs)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references | |
| RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Internet Standard | informatively references | |
| STD 66 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | informatively references | |
| STD 68 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Internet Standard | informatively references |