RFC 4690: Review and Recommendations for Internationalized Domain Names (IDNs)
In plain English — editorial summary, not part of the RFC
This note describes issues raised by the deployment and use of Internationalized Domain Names. It describes problems both at the time of registration and for use of those names in the DNS. It recommends that IETF should update the RFCs relating to IDNs and a framework to be followed in doing so, as well as summarizing and identifying some work that is required outside the IETF. In particular, it proposes that some changes be investigated for the Internationalizing Domain Names in Applications (IDNA) standard and its supporting tables, based on experience gained since those standards were completed. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4690
- Published
- September 2006
- Authors
- J. Klensin; P. Faltstrom; C. Karp; IAB
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5892The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)Updated
August 2010
- RFC 3172Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")Updated
September 2001
- RFC 9120Nameservers for the Address and Routing Parameter Area ("arpa") DomainCurrent
October 2021
- RFC 4703Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) ClientsCurrent
October 2006
- RFC 4641DNSSEC Operational PracticesObsoleted
September 2006
- RFC 4635HMAC SHA (Hashed Message Authentication Code, Secure Hash Algorithm) TSIG Algorithm IdentifiersObsoleted
August 2006
- RFC 4759The ENUM Dip Indicator Parameter for the "tel" URICurrent
December 2006
- RFC 4509Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs)Current
May 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?