References from draft-iesg-sponsoring-guidelines
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 | ||
BCP 26 |
References Referenced by |
normatively references | ||
BCP 78 |
References Referenced by |
informatively references | ||
BCP 9 |
References Referenced by |
normatively references | ||
BCP 92 |
References Referenced by |
normatively references | ||
BCP 97 |
References Referenced by |
informatively references | ||
draft-iab-rfc-editor |
The RFC Series and RFC Editor
References Referenced by |
Informational | informatively references | |
draft-ietf-proto-wgchair-doc-shepherding |
Document Shepherding from Working Group Last Call to Publication
References Referenced by |
Informational | normatively references | |
draft-klensin-rfc-independent |
Independent Submissions to the RFC Editor
References Referenced by |
informatively references | ||
RFC 2026 |
The Internet Standards Process -- Revision 3
References Referenced by |
Best Current Practice | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2434 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
RFC 3932 |
The IESG and RFC Editor Documents: Procedures
References Referenced by |
Best Current Practice | informatively references | |
RFC 3967 |
Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level
References Referenced by |
Best Current Practice | informatively references |