References from draft-alvestrand-i18n-howto
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 |
---|---|---|---|---|
draft-duerst-iri-bidi |
Internet Identifiers and Bidirectionality
References Referenced by |
Reference | ||
RFC 1521 |
MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies
References Referenced by |
Draft Standard | Reference | |
RFC 1685 |
Writing X.400 O/R Names
References Referenced by |
Informational | Possible Reference | |
RFC 2026 |
The Internet Standards Process -- Revision 3
References Referenced by |
Best Current Practice | Reference | |
RFC 2028 |
The Organizations Involved in the IETF Standards Process
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 | Reference | |
RFC 2234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Proposed Standard | Reference | |
RFC 2277 |
IETF Policy on Character Sets and Languages
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | Reference | |
RFC 2822 |
Internet Message Format
References Referenced by |
Proposed Standard | Possible Reference | |
RFC 2860 |
Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority
References Referenced by |
Informational | Reference | |
RFC 3066 |
Tags for the Identification of Languages
References Referenced by |
Best Current Practice | Possible Reference |