References from draft-nottingham-rss2
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 11 |
The Organizations Involved in the IETF Standards Process
References Referenced by |
Best Current Practice | Reference | |
| BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Reference | |
| BCP 47 |
Tags for Identifying Languages
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 2396 |
Uniform Resource Identifiers (URI): Generic Syntax
References Referenced by |
Draft Standard | Reference | |
| RFC 3023 |
XML Media Types
References Referenced by |
Proposed Standard | Reference | |
| RFC 3066 |
Tags for the Identification of Languages
References Referenced by |
Best Current Practice | Reference | |
| RFC 822 |
STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
References Referenced by |
Internet Standard | Possible Reference | |
| STD 11 |
STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
References Referenced by |
Internet Standard | Reference |