References from rfc3059
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 | Reference | |
| BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | Reference | |
| BCP 47 |
Tags for Identifying Languages
References Referenced by |
Best Current Practice | Reference | |
| BCP 9 |
Reducing the Standards Track to Two Maturity Levels
References Referenced by |
Best Current Practice | Reference | |
| RFC 2026 |
The Internet Standards Process -- Revision 3
References Referenced by |
Best Current Practice | Reference | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Possible Reference | |
| RFC 2608 |
Service Location Protocol, Version 2
References Referenced by |
Proposed Standard | Reference | |
| RFC 2609 |
Service Templates and Service: Schemes
References Referenced by |
Proposed Standard | Reference | |
| RFC 3066 |
Tags for the Identification of Languages
References Referenced by |
Best Current Practice | Reference |