To: IETF-Announce: ;
Subject: RFC 3743 on Joint Engineering Team (JET) Guidelines for Internationalized Domain Names (IDN) Registration and Administration for Chinese, Japanese, and Korean
Cc: rfc-editor@xxxxxxxxxxxxxx
From: rfc-editor@xxxxxxxxxxxxxx
Date: Wed, 14 Apr 2004 16:48:16 -0700
X-ISI-4-28-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@xxxxxxx
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on
ietf-mx.ietf.org
X-Spam-Status: No, hits=-9.1 required=5.0 tests=AWL,MIME_BOUND_NEXTPART,
NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Sender: ietf-announce-admin@xxxxxxxx
X-BeenThere: ietf-announce@xxxxxxxx
X-Mailman-Version: 2.0.12
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>,
<mailto:ietf-announce-request@xxxxxxxx?subject=unsubscribe>
List-Id: <ietf-announce.ietf.org>
List-Post: <mailto:ietf-announce@xxxxxxxx>
List-Help: <mailto:ietf-announce-request@xxxxxxxx?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>,
<mailto:ietf-announce-request@xxxxxxxx?subject=subscribe>
A new Request for Comments is now available in online RFC libraries.
RFC 3743
Title: Joint Engineering Team (JET) Guidelines for Internationalized Domain Names (IDN) Registration and Administration for Chinese, Japanese, and Korean Author(s): K. Konishi, K. Huang, H. Qian, Y. Ko Status: Informational Date: April 2004 Mailbox: konishi@xxxxxxxxxxx, huangk@xxxxxxxxxxxxxxx, Hlqian@xxxxxxxxxxxx, yw@xxxxxxxxxx Pages: 33 Characters: 74963 Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-jseng-idn-admin-05.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3743.txt
Achieving internationalized access to domain names raises many complex issues. These are associated not only with basic protocol design, such as how names are represented on the network, compared, and converted to appropriate forms, but also with issues and options for deployment, transition, registration, and administration.
The IETF Standards for Internationalized Domain Names, known as "IDNA", focuses on access to domain names in a range of scripts that is broader in scope than the original ASCII. The development process made it clear that use of characters with similar appearances and/or interpretations created potential for confusion, as well as difficulties in deployment and transition. The conclusion was that, while those issues were important, they could best be addressed administratively rather than through restrictions embedded in the protocols. This document defines a set of guidelines for applying restrictions of that type for Chinese, Japanese and Korean (CJK) scripts and the zones that use them and, perhaps, the beginning of a framework for thinking about other zones, languages, and scripts.
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@xxxxxxxxx Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@xxxxxxxxxxxxxxx
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@xxxxxxxxxxxxxx with the message body help: ways_to_get_rfcs. For example:
To: rfc-info@xxxxxxxxxxxxxx Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@xxxxxxxxxxxxxxx Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@xxxxxxxxxxxxxxx Please consult RFC 2223, Instructions to RFC Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
[The following attachment must be fetched by mail. Command-click the URL below and send the resulting message to get the attachment.]
<mailto:RFC-INFO@xxxxxxxxxxxxxx?body=RETRIEVE:%20rfc%0D%0ADOC-ID:%20rfc3743>
[The following attachment must be fetched by ftp. Command-click the URL below to ask your ftp client to fetch it.]
<ftp://ftp.isi.edu/in-notes/rfc3743.txt>