References from RFC 4290
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 47 |
References Referenced by |
informatively references | ||
BCP 78 |
References Referenced by |
informatively references | ||
RFC 1035 |
Domain names - implementation and specification
References Referenced by |
Internet Standard | informatively references | |
RFC 3066 |
Tags for the Identification of Languages
References Referenced by |
Best Current Practice | informatively references | |
RFC 3490 |
Internationalizing Domain Names in Applications (IDNA)
References Referenced by |
Proposed Standard | informatively references | |
RFC 3491 |
Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)
References Referenced by |
Proposed Standard | informatively references | |
RFC 3492 |
Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA)
References Referenced by |
Proposed Standard | informatively references | |
RFC 3536 |
Terminology Used in Internationalization in the IETF
References Referenced by |
Informational | informatively references | |
RFC 3743 |
Joint Engineering Team (JET) Guidelines for Internationalized Domain Names (IDN) Registration and Administration for Chinese, Japanese, and Korean
References Referenced by |
Informational | informatively references | |
RFC 3932 |
The IESG and RFC Editor Documents: Procedures
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 952 |
DoD Internet host table specification
References Referenced by |
Unknown | informatively references | |
STD 13 |
References Referenced by |
informatively references |