Suggested Practices for Registration of Internationalized Domain Names (IDN)
RFC 4290
Approval announcement
Draft of message to be sent after approval:
From: The IESG <iesg-secretary@ietf.org>
To: RFC Editor <rfc-editor@rfc-editor.org>
Cc: The IESG <iesg@ietf.org>, <iana@iana.org>, ietf-announce@ietf.org
Subject: Re: Informational RFC to be:
draft-klensin-reg-guidelines-09.txt
The IESG has no problem with the publication of 'Suggested Practices for
Registration of Internationalized Domain Names (IDN)'
<draft-klensin-reg-guidelines-09.txt> as an Informational RFC.
The IESG would also like the IRSG or RFC-Editor to review the comments in
the datatracker
(https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=10455&rfc_flag=0)
related to this document and determine whether or not they merit
incorporation into the document. Comments may exist in both the ballot
and the comment log.
The IESG contact person is Margaret Wasserman.
A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-klensin-reg-guidelines-09.txt
The process for such documents is described at http://www.rfc-editor.org/indsubs.html.
Thank you,
The IESG Secretary
Technical Summary
This document explores the issues in registration of
internationalized domain names (IDNs). The basic IDN definition
potentially allows a very large number of possible characters in
domain names, and this richness may lead to serious user confusion
about similar-looking names. To avoid this confusion, it is
necessary for the IDN registration process to impose rules that
disallow some otherwise-valid name combinations. This document
suggests a set of mechanisms that registries might use to define and
implement such rules, including adaptation of methods developed for
Chinese, Japanese, and Korean domain names to other languages and
scripts.
Working Group Summary
This is an RFC Edtior individual submission, not a WG work item.
Protocol Quality
This document was reviewed for the RFC Editor by Patrik Faltstom and
updated based on his feedback. He now claims that it is ready for
publication. I circulated this document to the DNS Directorate and
received no objections to publication. I have also reviewed the
document.
Note to RFC Editor
Dear RFC Editor,
The IESG has not found any conflict between this document and IETF
work. If you choose to publish this document, please do so with the
standard IESG Note included below.
Thank you!
IESG Note (for inclusion in the document)
This RFC is not a candidate for any level of Internet Standard.
The IETF disclaims any knowledge of the fitness of this RFC for
any purpose and notes that the decision to publish is not based on
IETF review apart from IESG review for conflict with IETF work.
The RFC Editor has chosen to publish this document at its
discretion. See RFC 3932 for more information.