References from RFC 4647
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 18 |
References Referenced by |
normatively references | ||
BCP 47 |
References Referenced by |
informatively references | ||
BCP 78 |
References Referenced by |
informatively references | ||
RFC 1766 |
Tags for the Identification of Languages
References Referenced by |
Proposed Standard | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2277 |
IETF Policy on Character Sets and Languages
References Referenced by |
Best Current Practice | normatively references | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | informatively references | |
RFC 3066 |
Tags for the Identification of Languages
References Referenced by |
Best Current Practice | informatively references | |
RFC 3282 |
Content Language Headers
References Referenced by |
Draft Standard | informatively references | |
RFC 4234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Draft Standard | normatively references | |
RFC 4646 |
Tags for Identifying Languages
References Referenced by |
Best Current Practice | informatively references |