RFC 3743技術(shù)標準翻譯
2022年09月13日 10:00
RFC 3743: Joint Engineering Team (JET) Guidelines for Internationalized Domain Names (IDN) Registration and Administration for Chinese, Japanese, and Korean 中文翻譯
URL : https://datatracker.ietf.org/doc/html/rfc3743
標題 : RFC 3743
翻譯類型 : 自動生成
Network Working Group K. Konishi
Request for Comments: 3743 K. Huang
Category: Informational H. Qian
Y. Ko
April 2004
Network Working Group K. Konishi
Request for Comments: 3743 K. Huang
Category: Informational H. Qian
Y. Ko
April 2004
Joint Engineering Team (JET) Guidelines for Internationalized Domain Names (IDN) Registration and Administration for Chinese, Japanese, and Korean
聯(lián)合工程團隊（JET）中文、日文和韓文國際化域名（IDN）注冊和管理指南
Status of this Memo
本備忘錄的狀況
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本備忘錄為互聯(lián)網(wǎng)社區(qū)提供信息。它沒有規(guī)定任何類型的互聯(lián)網(wǎng)標準。本備忘錄的分發(fā)不受限制。
Copyright Notice
版權(quán)公告
Copyright (C) The Internet Society (2004). All Rights Reserved.
版權(quán)所有（C）互聯(lián)網(wǎng)協(xié)會（2004年）。版權(quán)所有。
IESG Note
IESG注釋
The IESG congratulates the Joint Engineering Team (JET) on developing mechanisms to enforce their desired policy. The Language Variant Table mechanisms described here allow JET to enforce language-based character variant preferences, and they set an example for those who might want to use variant tables for their own policy enforcement.
IESG祝賀聯(lián)合工程團隊（JET）制定了執(zhí)行其預期政策的機制。這里描述的語言變體表機制允許JET強制執(zhí)行基于語言的字符變體首選項，它們?yōu)槟切┛赡芟Ｍ褂米凅w表強制執(zhí)行自己策略的人樹立了榜樣。
The IESG encourages those following this example to take JET's diligence as an example, as well as its technical work. To follow their example, registration authorities may need to articulate policy, develop appropriate procedures and mechanisms for enforcement, and document the relationship between the two. JET's LVT mechanism should be adaptable to different policies, and can be considered during that development process.
IESG鼓勵那些遵循此示例的人以JET的勤奮以及其技術(shù)工作為例。為了仿效他們的榜樣，登記當局可能需要闡明政策，制定適當?shù)某绦蚝蛨?zhí)行機制，并記錄兩者之間的關(guān)系。JET的LVT機制應(yīng)該適應(yīng)不同的政策，并且可以在開發(fā)過程中加以考慮。
The IETF does not, of course, dictate policy or require the use of any particular mechanisms for the implementation of these policies, as these are matters of sovereignty and contract.
當然，IETF不規(guī)定政策或要求使用任何特定機制來實施這些政策，因為這些是主權(quán)和合同問題。
Abstract
摘要
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.
實現(xiàn)域名的國際化訪問提出了許多復雜的問題。這些問題不僅與基本協(xié)議設(shè)計相關(guān)，例如名稱在網(wǎng)絡(luò)上的表示、比較和轉(zhuǎn)換為適當形式的方式，還與部署、轉(zhuǎn)換、注冊和管理的問題和選項相關(guān)。
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.
IETF的國際化域名標準（稱為“IDNA”）側(cè)重于在一系列腳本中訪問域名，這些腳本的范圍比原始ASCII更廣。發(fā)展過程清楚地表明，使用具有相似外觀和/或解釋的角色可能會造成混淆，以及部署和過渡方面的困難。結(jié)論是，雖然這些問題很重要，但最好通過行政手段而不是通過議定書中的限制來解決。本文檔定義了一套指南，用于對中文、日文和韓文（CJK）腳本和使用它們的區(qū)域應(yīng)用此類限制，并且可能是思考其他區(qū)域、語言和腳本的框架的開始。
Table of Contents
目錄
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Definitions, Context, and Notation . . . . . . . . . . . . . . 5
2.1. Definitions and Context. . . . . . . . . . . . . . . . . 5
2.2. Notation for Ideographs and Other Non-ASCII CJK
Characters . . . . . . . . . . . . . . . . . . . . . . . 9
3. Scope of the Administrative Guidelines . . . . . . . . . . . . 9
3.1. Principles Underlying These Guidelines . . . . . . . . . 10
3.2. Registration of IDL. . . . . . . . . . . . . . . . . . . 13
3.2.1. Using the Language Variant Table . . . . . . . . 13
3.2.2. IDL Package. . . . . . . . . . . . . . . . . . . 14
3.2.3. Procedure for Registering IDLs . . . . . . . . . 14
3.3. Deletion and Transfer of IDL and IDL Package . . . . . . 19
3.4. Activation and Deactivation of IDL Variants . . . . . . 19
3.4.1. Activation Algorithm . . . . . . . . . . . . . . 19
3.4.2. Deactivation Algorithm . . . . . . . . . . . . . 20
3.5. Managing Changes in Language Associations. . . . . . . . 21
3.6. Managing Changes to Language Variant Tables. . . . . . . 21
4. Examples of Guideline Use in Zones . . . . . . . . . . . . . . 21
5. Syntax Description for the Language Variant Table. . . . . . . 25
5.1. ABNF Syntax. . . . . . . . . . . . . . . . . . . . . . . 25
5.2. Comments and Explanation of Syntax . . . . . . . . . . . 25
6. Security Considerations. . . . . . . . . . . . . . . . . . . . 27
7. Index to Terminology . . . . . . . . . . . . . . . . . . . . . 27
8. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 28
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
9.1. Normative References . . . . . . . . . . . . . . . . . . 29
9.2. Informative References . . . . . . . . . . . . . . . . . 30
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 30
10.1. Authors' Addresses . . . . . . . . . . . . . . . . . . . 31
10.2. Editors' Addresses . . . . . . . . . . . . . . . . . . . 32
11. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 33
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Definitions, Context, and Notation . . . . . . . . . . . . . . 5
2.1. Definitions and Context. . . . . . . . . . . . . . . . . 5
2.2. Notation for Ideographs and Other Non-ASCII CJK
Characters . . . . . . . . . . . . . . . . . . . . . . . 9
3. Scope of the Administrative Guidelines . . . . . . . . . . . . 9
3.1. Principles Underlying These Guidelines . . . . . . . . . 10
3.2. Registration of IDL. . . . . . . . . . . . . . . . . . . 13
3.2.1. Using the Language Variant Table . . . . . . . . 13
3.2.2. IDL Package. . . . . . . . . . . . . . . . . . . 14
3.2.3. Procedure for Registering IDLs . . . . . . . . . 14
3.3. Deletion and Transfer of IDL and IDL Package . . . . . . 19
3.4. Activation and Deactivation of IDL Variants . . . . . . 19
3.4.1. Activation Algorithm . . . . . . . . . . . . . . 19
3.4.2. Deactivation Algorithm . . . . . . . . . . . . . 20
3.5. Managing Changes in Language Associations. . . . . . . . 21
3.6. Managing Changes to Language Variant Tables. . . . . . . 21
4. Examples of Guideline Use in Zones . . . . . . . . . . . . . . 21
5. Syntax Description for the Language Variant Table. . . . . . . 25
5.1. ABNF Syntax. . . . . . . . . . . . . . . . . . . . . . . 25
5.2. Comments and Explanation of Syntax . . . . . . . . . . . 25
6. Security Considerations. . . . . . . . . . . . . . . . . . . . 27
7. Index to Terminology . . . . . . . . . . . . . . . . . . . . . 27
8. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 28
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
9.1. Normative References . . . . . . . . . . . . . . . . . . 29
9.2. Informative References . . . . . . . . . . . . . . . . . 30
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 30
10.1. Authors' Addresses . . . . . . . . . . . . . . . . . . . 31
10.2. Editors' Addresses . . . . . . . . . . . . . . . . . . . 32
11. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 33
1. Introduction
1. 介紹
Domain names form the fundamental naming architecture of the Internet. Countless Internet protocols and applications rely on them, not just for stability and continuity, but also to avoid ambiguity. They were designed to be identifiers without any language context. However, as domain names have become visible to end users through Web URLs and e-mail addresses, the strings in domain-name labels are being increasingly interpreted as names, words, or phrases. It is likely that users will do the same with languages of differing character sets, such as Chinese, Japanese and Korean (CJK), in which many words or concepts are represented using short sequences of characters.
域名構(gòu)成了互聯(lián)網(wǎng)的基本命名架構(gòu)。無數(shù)的互聯(lián)網(wǎng)協(xié)議和應(yīng)用程序依賴于它們，這不僅是為了穩(wěn)定性和連續(xù)性，也是為了避免歧義。它們被設(shè)計成沒有任何語言背景的標識符。然而，隨著最終用戶通過Web URL和電子郵件地址看到域名，域名標簽中的字符串越來越多地被解釋為名稱、單詞或短語。用戶可能會對不同字符集的語言（如中文、日文和韓文（CJK））采取同樣的做法，在這些語言中，許多單詞或概念都是使用短字符序列表示的。
The introduction of what are called Internationalized Domain Names (IDN) amplifies both the difficulty of putting names into identifiers and the confusion that exists between scripts and languages. Character symbols that appear (or actually are) identical, or that have similar or identical semantics but that are assigned the different code points, further increase the potential for confusion. DNS internationalization also affects a number of Internet protocols and applications and creates additional layers of complexity in terms of technical administration and services. Given the added complications of using a much broader range of characters than the original small ASCII subset, precautions are necessary in the deployment of IDNs in order to minimize confusion and fraud.
所謂的國際化域名（IDN）的引入既增加了將名稱放入標識符的難度，也增加了腳本和語言之間存在的混淆?？雌饋恚ɑ?qū)嶋H上）相同的字符符號，或具有相似或相同語義但分配了不同代碼點的字符符號，進一步增加了混淆的可能性。DNS國際化還影響許多互聯(lián)網(wǎng)協(xié)議和應(yīng)用程序，并在技術(shù)管理和服務(wù)方面造成額外的復雜性。由于使用比原來的小ASCII子集更廣泛的字符范圍會增加復雜性，因此在部署IDN時必須采取預防措施，以最大限度地減少混淆和欺詐。
The IETF IDN Working Group [IDN-WG] addressed the problem of handling the encoding and decoding of Unicode strings into and out of Domain Name System (DNS) labels with the goal that its solution would not put the operational DNS at any risk. Its work resulted in one primary protocol and three supporting ones, respectively:
IETF IDN工作組[IDN-WG]解決了處理Unicode字符串進出域名系統(tǒng)（DNS）標簽的編碼和解碼問題，其目標是其解決方案不會使操作DNS面臨任何風險。其工作分別產(chǎn)生了一個主要協(xié)議和三個支持協(xié)議：
1. Internationalizing Host Names in Applications [IDNA] 2. Preparation of Internationalized Strings [STRINGPREP] 3. A Stringprep Profile for Internationalized Domain Names [NAMEPREP] 4. Punycode [PUNYCODE]
1. 國際化應(yīng)用程序中的主機名[IDNA]2。準備國際化字符串[STRINGPREP]3。國際化域名的Stringprep配置文件[NAMEPREP]4。Punycode[Punycode]
IDNA, which calls on the others, normalizes and transforms strings that are intended to be used as IDNs. In combination, the four provide the minimum functions required for internationalization, such as performing case mappings, eliminating character differences that would cause severe problems, and specifying matching (equality). They also convert between the resulting Unicode code points and an ASCII-based form that is more suitable for storing in actual DNS labels. In this way, the IDNA transformations improve a user's chances of getting to the correct IDN.
IDNA調(diào)用其他函數(shù)，對用作IDN的字符串進行規(guī)范化和轉(zhuǎn)換。這四種方法結(jié)合起來提供了國際化所需的最低功能，例如執(zhí)行大小寫映射、消除可能導致嚴重問題的字符差異以及指定匹配（相等）。它們還可以在生成的Unicode代碼點和更適合存儲在實際DNS標簽中的基于ASCII的形式之間進行轉(zhuǎn)換。這樣，IDNA轉(zhuǎn)換提高了用戶獲得正確IDN的機會。
Addressing the issues around differing character sets, a primary consideration and administrative challenge involves region-specific definitions, interpretations, and the semantics of strings to be used in IDNs. A Unicode string may have a specific meaning as a name, word, or phrase in a particular language but that meaning could vary depending on the country, region, culture, or other context in which the string is used. It might also have different interpretations in different languages that share some or all of the same characters. Therefore, individual zones and zone administrators may find it necessary to impose restrictions and procedures to reduce the likelihood of confusion, and instabilities of reference, within their own environments.
解決不同字符集的問題，主要考慮和管理挑戰(zhàn)涉及IDN中使用的特定于區(qū)域的定義、解釋和字符串語義。Unicode字符串可能具有特定的含義，如特定語言中的名稱、單詞或短語，但該含義可能因使用該字符串的國家、地區(qū)、文化或其他上下文而異。它也可能在不同的語言中有不同的解釋，這些語言共享一些或所有相同的字符。因此，各個區(qū)域和區(qū)域管理員可能會發(fā)現(xiàn)有必要實施限制和程序，以減少在其自身環(huán)境中出現(xiàn)混淆和參考不穩(wěn)定性的可能性。
Over the centuries, the evolution of CJK characters, and the differences in their use in different languages and even in different regions where the same language is spoken, has given rise to the idea of "variants", wherein one conceptual character can be identified with several different Code Points in character sets for computer use. This document provides a framework for handling such variants while minimizing the possibility of serious user confusion in the obtaining or using of domain names. However, the concept of variants is complex and may require many different layers of solutions. This guideline offers only one of those solution components. It is not sufficient by itself to solve the whole problem, even with zone-specific tables as described below.
幾個世紀以來，CJK字符的演變，以及它們在不同語言中甚至在使用同一語言的不同地區(qū)的使用差異，產(chǎn)生了“變體”的概念，其中一個概念性字符可以通過字符集中的幾個不同代碼點來識別，以供計算機使用。本文檔提供了一個處理此類變體的框架，同時最大限度地減少了用戶在獲取或使用域名時嚴重混淆的可能性。然而，變體的概念很復雜，可能需要許多不同層次的解決方案。本指南僅提供其中一個解決方案組件。單靠它本身還不足以解決整個問題，即使使用下面描述的特定于區(qū)域的表也是如此。
Additionally, because of local language or writing-system differences, it is impossible to create universally accepted definitions for which potential variants are the same and which are not the same. It is even more difficult to define a technical algorithm to generate variants that are linguistically accurate. That is, that the variant forms produced make as much sense in the language as the originally specified forms. It is also possible that variants generated may have no meaning in the associated language or languages. The intention is not to generate meaningful "words" but to generate similar variants to be reserved. So even though the method described in this document may not always be linguistically accurate, nor does it need to be, it increases the chances of getting the right variants while accepting the inherent limitations of the DNS and the complexities of human language.
此外，由于當?shù)卣Z言或書寫系統(tǒng)的差異，不可能為潛在變體相同和不同的變體創(chuàng)建普遍接受的定義。更難定義一種技術(shù)算法來生成語言準確的變體。也就是說，產(chǎn)生的變體形式在語言中與最初指定的形式一樣有意義。生成的變體也可能在相關(guān)語言中沒有意義。其目的不是生成有意義的“單詞”，而是生成要保留的類似變體。因此，盡管本文檔中描述的方法在語言上可能并不總是準確的，也不一定是準確的，但它增加了獲得正確變體的機會，同時接受DNS固有的局限性和人類語言的復雜性。
This document outlines a model for such conventions for zones in which labels that contain CJK characters are to be registered and a system for implementing that model. It provides a mechanism that allows each zone to define its own local rules for permitted characters and sequences and the handling of IDNs and their variants.
本文檔概述了將在其中注冊包含CJK字符的標簽的區(qū)域的此類約定的模型以及用于實現(xiàn)該模型的系統(tǒng)。它提供了一種機制，允許每個區(qū)域為允許的字符和序列以及IDN及其變體的處理定義自己的本地規(guī)則。
The document is an effort of the Joint Engineering Team (JET), a group composed of members of CNNIC, TWNIC, KRNIC, and JPNIC as well as other individual experts. It offers guidelines for zone administrators, including but not limited to registry operators and registrars and information for all domain names holders on the administration of domain names that contain characters drawn from Chinese, Japanese, and Korean scripts. Other language groups are encouraged to develop their own guidelines as needed, based on these guidelines if that is helpful.
該文件是聯(lián)合工程團隊（JET）的成果，該團隊由CNNIC、TWNIC、KRNIC和JPNIC的成員以及其他個人專家組成。它為區(qū)域管理員（包括但不限于注冊運營商和注冊商）提供了指南，并為所有域名持有人提供了關(guān)于管理包含中文、日文和韓文字符的域名的信息。鼓勵其他語言團體根據(jù)需要制定自己的指導方針，如果這些指導方針有用的話。
2. Definitions, Context, and Notation
2. 定義、上下文和符號
2.1. Definitions and Context
2.1. 定義和背景
This document uses a number of special terms. In this section, definitions and explanations are grouped topically. Some readers may prefer to skip over this material, returning, perhaps via the index to terminology in section 7, when needed.
本文件使用了一些特殊術(shù)語。在本節(jié)中，定義和解釋按主題分組。有些讀者可能更愿意跳過本資料，在需要時，可以通過第7節(jié)中的術(shù)語索引返回。
2.1.1. IDN
2.1.1. IDN
IDN: The term "IDN" has a number of different uses: (a) as an abbreviation for "Internationalized Domain Name"; (b) as a fully qualified domain name that contains at least one label that contains characters not appearing in ASCII, specifically not in the subset of ASCII recommended for domain names (the so-called "hostname" or "LDH" subset, see RFC1035 [STD13]); (c) as a label of a domain name that contains at least one character beyond ASCII; (d) as a Unicode string to be processed by Nameprep; (e) as a string that is an output from Nameprep; (f) as a string that is the result of processing through both Nameprep and conversion into Punycode; (g) as the abbreviation of an IDN (more properly, IDL) Package, in the terminology of this document; (h) as the abbreviation of the IETF IDN Working Group; (g) as the abbreviation of the ICANN IDN Committee; and (h) as standing for other IDN activities in other companies/organizations.
IDN：術(shù)語“IDN”有許多不同的用途：（a）作為“國際化域名”的縮寫；（b） 作為一個完全限定的域名，至少包含一個標簽，其中包含ASCII中未出現(xiàn)的字符，特別是未出現(xiàn)在為域名推薦的ASCII子集（所謂的“主機名”或“LDH”子集，請參見RFC1035[STD13]）；（c） 作為域名的標簽，至少包含ASCII以外的一個字符；（d） 作為要由Nameprep處理的Unicode字符串；（e） 作為Nameprep輸出的字符串；（f） 作為通過Nameprep和轉(zhuǎn)換為Punycode處理的結(jié)果的字符串；（g） 作為IDN（更準確地說，IDL）包的縮寫，在本文件術(shù)語中；（h） 作為IETF IDN工作組的縮寫；（g） 作為ICANN IDN委員會的縮寫；（h）代表其他公司/組織的其他IDN活動。
Because of the potential confusion, this document uses the term "IDN" as an abbreviation for Internationalized Domain Name and, specifically, in the second sense described in (b) above. It uses "IDL," defined immediately below, to refer to Internationalized Domain Labels.
由于潛在的混淆，本文件使用術(shù)語“IDN”作為國際化域名的縮寫，具體而言，是上文（b）中所述的第二種含義。它使用下面定義的“IDL”來表示國際化的域標簽。
2.1.2. IDL
2.1.2. IDL
IDL: This document provides a guideline to be applied on a per-zone basis, one label at a time. Therefore, the term "Internationalized Domain Label" or "IDL" will be used instead of the more general term "IDN" or its equivalents. The processing specifications of this
IDL：本文件提供了一個指南，以每個區(qū)域為基礎(chǔ)，每次使用一個標簽。因此，將使用術(shù)語“國際化域標簽”或“IDL”，而不是更一般的術(shù)語“IDN”或其等價物。本產(chǎn)品的加工規(guī)格
document may be applied, in some zones, to ASCII characters also, if those characters are specified as valid in a Language Variant Table (see below). Hence, in some zones, an IDL may contain or consist entirely of "LDH" characters.
在某些區(qū)域，如果ASCII字符在語言變量表中被指定為有效字符，則文檔也可以應(yīng)用于ASCII字符（見下文）。因此，在某些區(qū)域中，IDL可能包含或完全由“LDH”字符組成。
2.1.3. FQDN
2.1.3. FQDN
FQDN: A fully qualified domain name, one that explicitly contains all labels, including a Top-Level Domain (TLD) name. In this context, a TLD name is one whose label appears in a nameserver record in the root zone. The term "Domain Name Label" refers to any label of a FQDN.
FQDN：完全限定的域名，顯式包含所有標簽，包括頂級域名（TLD）。在此上下文中，TLD名稱是其標簽出現(xiàn)在根區(qū)域的名稱服務(wù)器記錄中的名稱。術(shù)語“域名標簽”指FQDN的任何標簽。
2.1.4. Registrations
2.1.4. 注冊
Registration: In this document, the term "registration" refers to the process by which a potential domain name holder requests that a label be placed in the DNS either as an individual name within a domain or as a subdomain delegation from another domain name holder. In the case of a successful registration, the label or delegation records are placed in the relevant zone file, or, more specifically, they are "activated" or made "active" and additional IDLs may be reserved as part of an "IDL Package" (see below). The guidelines presented here are recommended for all zones, at any hierarchy level, in which CJK characters are to appear and not just domains at the first or second level.
注冊：在本文件中，術(shù)語“注冊”是指潛在域名持有人請求將標簽作為域內(nèi)的個人名稱或另一域名持有人的子域授權(quán)放置在DNS中的過程。在成功注冊的情況下，標簽或授權(quán)記錄被放置在相關(guān)區(qū)域文件中，或者更具體地說，它們被“激活”或被設(shè)置為“激活”，并且額外的IDL可以作為“IDL包”的一部分保留（見下文）。此處提供的指南建議用于所有區(qū)域，在任何層次結(jié)構(gòu)級別，其中將顯示CJK字符，而不僅僅是第一級或第二級的域。
2.1.5. RFC3066
2.1.5. RFC3066
RFC3066: A system, widely used in the Internet, for coding and representing names of languages [RFC3066]. It is based on an International Organization for Standardization (ISO) standard for coding language names [ISO639], but expands it to provide additional precision.
RFC3066：互聯(lián)網(wǎng)上廣泛使用的一種系統(tǒng)，用于編碼和表示語言名稱[RFC3066]。它基于國際標準化組織（ISO）的語言名稱編碼標準[ISO639]，但對其進行了擴展以提供額外的精度。
2.1.6. ISO/IEC 10646
2.1.6. ISO/IEC 10646
ISO/IEC 10646: The international standard universal multiple-octet coded character set ("UCS") [IS10646]. The Code Point definitions of this standard are identical to those of corresponding versions of the Unicode standard (see below). Consequently, the characters and their coding are often referred to as "Unicode characters."
ISO/IEC 10646：國際標準通用多八位編碼字符集（“UCS”）[IS10646]。本標準的代碼點定義與Unicode標準相應(yīng)版本的代碼點定義相同（見下文）。因此，字符及其編碼通常被稱為“Unicode字符”
2.1.7. Unicode Character
2.1.7. Unicode字符
Unicode Character: The term "Unicode character" is used here in reference to characters chosen from the Unicode Standard Version 3.2 [UNICODE] (and hence from ISO/IEC 10646). In this document, the
Unicode字符：這里使用術(shù)語“Unicode字符”指的是從Unicode標準版本3.2[Unicode]（以及ISO/IEC 10646）中選擇的字符。在本文件中
characters are identified by their positions, or "Code Points." The notation U+12AB, for example, indicates the character at the position 12AB (hexadecimal) in the Unicode 3.2 table. For characters in positions above FFFF, i.e., requiring more than sixteen bits to represent, a five to eight-character string is used, such as U+112AB for the character in position 12AB of plane 1.
字符由其位置或“代碼點”標識。例如，符號U+12AB表示Unicode 3.2表中12AB（十六進制）位置的字符。對于FFFF以上位置的字符，即需要超過16位來表示的字符，使用5到8個字符串，例如平面1的12AB位置的字符使用U+112AB。
2.1.8. Unicode String
2.1.8. Unicode字符串
Unicode String: "Unicode string" refers to a string of Unicode characters. The Unicode string is identified by the sequence of the Unicode characters regardless of the encoding scheme.
Unicode字符串：“Unicode字符串”是指Unicode字符的字符串。Unicode字符串由Unicode字符序列標識，而與編碼方案無關(guān)。
2.1.9. CJK Characters
2.1.9. CJK字符
CJK Characters: CJK characters are characters commonly used in the Chinese, Japanese, or Korean languages, including but not limited to those defined in the Unicode Standard as ASCII (U+0020 to U+007F), Han ideographs (U+3400 to U+9FAF and U+20000 to U+2A6DF), Bopomofo (U+3100 to U+312F and U+31A0 to U+31BF), Kana (U+3040 to U+30FF), Jamo (U+1100 to 11FF and U+3130 to U+318F), Hangul (U+AC00 to U+D7AF and U+3130 to U+318F), and the respective compatibility forms. The particular characters that are permitted in a given zone are specified in the Language Variant Table(s) for that zone.
CJK字符：CJK字符是中文、日文或韓文中常用的字符，包括但不限于Unicode標準中定義的ASCII（U+0020至U+007F）、漢字（U+3400至U+9FAF和U+20000至U+2A6DF）、Bopomofo（U+3100至U+312F和U+31A0至U+31BF）、假名（U+3040至U+30FF）、Jamo（U+1100至11FF和U+3130至U+318F）、韓語（U+AC00至U+D7AF和U+3130至U+318F）以及相應(yīng)的兼容格式。給定區(qū)域中允許的特定字符在該區(qū)域的語言變體表中指定。
2.1.10. Label String
2.1.10. 標簽串
Label String: A generic term referring to a string of characters that is a candidate for registration in the DNS or such a string, once registered. A label string may or may not be valid according to the rules of this specification and may even be invalid for IDNA use. The term "label", by itself, refers to a string that has been validated and may be formatted to appear in a DNS zone file.
標簽字符串：一個通用術(shù)語，指在DNS中注冊的候選字符串或此類字符串，一旦注冊。根據(jù)本規(guī)范的規(guī)則，標簽字符串可能有效，也可能無效，甚至可能對IDNA使用無效。術(shù)語“標簽”本身指的是已驗證的字符串，可以格式化為顯示在DNS區(qū)域文件中。
2.1.11. Language Variant Table
2.1.11. 語言變體表
Language Variant Table: The key mechanisms of this specification utilize a three-column table, called a Language Variant Table, for each language permitted to be registered in the zone. Those columns are known, respectively, as "Valid Code Point", "Preferred Variant", and "Character Variant", which are defined separately below. The Language Variant Tables are critical to the success of the guideline described in this document. However, the principles to be used to generate the tables are not within the scope of this document and should be worked out by each registry separately (perhaps by adopting or adapting the work of some other registry). In this document, "Table" and "Variant Table" are used as short forms for Language Variant Table.
語言變體表：本規(guī)范的關(guān)鍵機制為允許在區(qū)域中注冊的每種語言使用一個稱為語言變體表的三列表。這些列分別稱為“有效代碼點”、“首選變量”和“字符變量”，它們在下面分別定義。語言變體表對于本文件中所述指南的成功至關(guān)重要。然而，用于生成表格的原則不在本文件的范圍內(nèi)，應(yīng)由每個登記處單獨制定（也許通過采納或調(diào)整其他登記處的工作）。在本文件中，“表格”和“變體表格”用作語言變體表格的縮寫形式。
2.1.12. Valid Code Point
2.1.12. 有效代碼點
Valid Code Point: In a Language Variant Table, the list of Code Points that is permitted for that language. Any other Code Points, or any string containing them, will be rejected by this specification. The Valid Code Point list appears as the first column of the Language Variant Table.
有效代碼點：在語言變體表中，該語言允許的代碼點列表。本規(guī)范將拒絕任何其他代碼點或包含它們的任何字符串。有效代碼點列表顯示為語言變量表的第一列。
2.1.13. Preferred Variant
2.1.13. 首選變體
Preferred Variant: In a Language Variant Table, a list of Code Points corresponding to each Valid Code Point and providing possible substitutions for it. These substitutions are "preferred" in the sense that the variant labels generated using them are normally registered in the zone file, or "activated." The Preferred Code Points appear in column 2 of the Language Variant Table. "Preferred Code Point" is used interchangeably with this term.
首選變體：在語言變體表中，與每個有效代碼點對應(yīng)的代碼點列表，并為其提供可能的替換。這些替換是“首選”的，因為使用它們生成的變體標簽通常在區(qū)域文件中注冊或“激活”。首選代碼點顯示在語言變體表的第2列中?！笆走x代碼點”可與本術(shù)語互換使用。
2.1.14. Character Variant
2.1.14. 字符變體
Character Variant: In a Language Variant Table, a second list of Code Points corresponding to each Valid Code Point and providing possible substitutions for it. Unlike the Preferred Variants, substitutions based on Character Variants are normally reserved but not actually registered (or "activated"). Character Variants appear in column 3 of the Language Variant Table. The term "Code Point Variants" is used interchangeably with this term.
字符變體：在語言變體表中，對應(yīng)于每個有效代碼點的第二個代碼點列表，并為其提供可能的替換。與首選變體不同，基于字符變體的替換通常是保留的，但實際上沒有注冊（或“激活”）。字符變體出現(xiàn)在語言變體表的第3列中。術(shù)語“代碼點變體”可與該術(shù)語互換使用。
2.1.15. Preferred Variant Label
2.1.15. 首選變體標簽
Preferred Variant Label: A label generated by use of Preferred Variants (or Preferred Code Points).
首選變體標簽：使用首選變體（或首選代碼點）生成的標簽。
2.1.16. Character Variant Label
2.1.16. 字符變體標簽
Character Variant Label: A label generated by use of Character Variants.
字符變體標簽：使用字符變體生成的標簽。
2.1.17. Zone Variant
2.1.17. 區(qū)域變量
Zone Variant: A Preferred or Character Variant Label that is actually to be entered (registered) into the DNS. That is, into the zone file for the relevant zone. Zone Variants are also referred to as Zone Variant Labels or Active (or Activated) Labels.
區(qū)域變體：實際要輸入（注冊）到DNS中的首選或字符變體標簽。也就是說，輸入相關(guān)分區(qū)的分區(qū)文件。分區(qū)變量也稱為分區(qū)變量標簽或活動（或激活）標簽。
2.1.18. IDL Package
2.1.18. IDL包
IDL Package: A collection of IDLs as determined by these Guidelines. All labels in the package are "reserved", meaning they cannot be registered by anyone other than the holder of the Package. These reserved IDLs may be "activated", meaning they are actually entered into a zone file as a "Zone Variant". The IDL Package also contains identification of the language(s) associated with the registration process. The IDL and its variant labels form a single, atomic unit.
IDL包：由這些指南確定的IDL集合。包裝中的所有標簽都是“保留”的，這意味著除了包裝持有者之外，任何人都不能注冊這些標簽。這些保留IDL可能被“激活”，這意味著它們實際上作為“區(qū)域變量”輸入到區(qū)域文件中。IDL包還包含與注冊過程相關(guān)的語言標識。IDL及其變體標簽構(gòu)成一個單一的原子單元。
2.2. Notation for Ideographs and Other Non-ASCII CJK Characters.
2.2. 表意文字和其他非ASCII CJK字符的符號。
For purposes of clarity, particularly in regard to examples, Han ideographs appear in several places in this document. However, they do not appear in the ASCII version of this document. For the convenience of readers of the ASCII version, and some readers not familiar with recognizing and distinguishing Chinese characters, most uses of these characters will be associated with both their Unicode Code Points and an "asterisk tag" with its corresponding Chinese Romanization [ISO7098], with the tone mark represented by a number from 1 to 4. Those tags have no meaning outside this document; they are a quick visual and reading reference to help facilitate the combinations and transformations of characters in the guideline and table excerpts.
為清晰起見，尤其是在示例方面，本文件中的幾個地方出現(xiàn)了漢字。但是，它們不會出現(xiàn)在本文檔的ASCII版本中。為了方便ASCII版本的讀者，以及一些不熟悉識別和區(qū)分漢字的讀者，這些漢字的大多數(shù)用法都將與其Unicode代碼點和帶有相應(yīng)中文羅馬化的“星號標記”相關(guān)聯(lián)[ISO7098]，帶有由1到4之間的數(shù)字表示的音調(diào)標記。這些標簽在本文件之外沒有任何意義；它們是一個快速的視覺和閱讀參考，有助于促進指南和表格摘錄中字符的組合和轉(zhuǎn)換。
3. Scope of the Administrative Guidelines
3. 行政準則的范圍
Zone administrators are responsible for the administration of the domain name labels under their control. A zone administrator might be responsible for a large zone, such as a top-level domain (TLD), whether generic or country code, or a smaller one, such as a typical second- or third-level domain. A large zone is often more complex than its smaller counterpart. However, actual technical administrative tasks, such as addition, deletion, delegation, and transfer of zones between domain name holders, are similar for all zones.
區(qū)域管理員負責管理其控制下的域名標簽。區(qū)域管理員可能負責大型區(qū)域，例如頂級域（TLD），無論是通用代碼還是國家代碼，也可能負責較小的區(qū)域，例如典型的二級或三級域。大區(qū)域往往比小區(qū)域更復雜。然而，實際的技術(shù)管理任務(wù)，如添加、刪除、委派和域名持有者之間的區(qū)域轉(zhuǎn)移，對于所有區(qū)域都是類似的。
This document provides guidelines for the ways CJK characters should be handled within a zone, for how language issues should be considered and incorporated, and for how Domain Name Labels containing CJK characters should be administered (including registration, deletion, and transfer of labels).
本文檔提供了在區(qū)域內(nèi)處理CJK字符的方法、如何考慮和合并語言問題以及如何管理包含CJK字符的域名標簽（包括標簽的注冊、刪除和轉(zhuǎn)移）的指南。
Other IDN policies, such as the creation of new top-level domains (TLDs), the cost structure for registrations, and how the processes described here get allocated between registrar and registry if the zone makes that distinction, also are outside the scope of this document.
其他IDN政策，如創(chuàng)建新的頂級域（TLD）、注冊的成本結(jié)構(gòu)，以及如果區(qū)域做出區(qū)分，此處描述的流程如何在注冊商和注冊商之間分配，也不在本文檔的范圍內(nèi)。
Technical implementation issues are not discussed here either. For example, deciding which guidelines should be implemented as registry actions and which should be registrar actions is left to zone administrators, with the possibility that it will differ from zone to zone.
這里也不討論技術(shù)實現(xiàn)問題。例如，決定哪些指南應(yīng)作為注冊表操作實施，哪些指南應(yīng)作為注冊器操作實施，則留給區(qū)域管理員來決定，這可能會因區(qū)域而異。
3.1. Principles Underlying These Guidelines
3.1. 這些準則的基本原則
In many places, in the event of a dispute over rights to a name (or, more accurately, DNS label string), this document assumes "first-come, first-served" (FCFS) as a resolution policy even though FCFS is not listed below as one of the principles for this document. If policies are already in place governing priorities and "rights", one can use the guidelines here by replacing uses of FCFS in this document with policies specific to the zone. Some of the guidelines here may not be applicable to other policies for determining rights to labels. Still other alternatives, such as use of UDRP [UDRP] or mutual exclusion, might have little impact on other aspects of these guidelines.
在許多地方，如果對名稱（或更準確地說，DNS標簽字符串）的權(quán)利發(fā)生爭議，本文檔假定“先到先得”（FCFS）為解決策略，即使FCFS未列為本文檔的原則之一。如果已經(jīng)制定了管理優(yōu)先權(quán)和“權(quán)利”的政策，則可以使用此處的指南，將本文件中FCF的使用替換為特定于該區(qū)域的政策。此處的一些指南可能不適用于確定標簽權(quán)利的其他政策。還有其他替代方案，如使用UDRP[UDRP]或互斥，可能對這些指南的其他方面影響不大。
(a) Although some Unicode strings may be pure identifiers made up of an assortment of characters from many languages and scripts, IDLs are likely to be "words" or "names" or "phrases" that have specific meaning in a language. While a zone administration might or might not require "meaning" as a registration criterion, meaning could prove to be a useful tool for avoiding user confusion.
(a) 盡管某些Unicode字符串可能是由多種語言和腳本中的各種字符組成的純標識符，但IDL可能是在某種語言中具有特定含義的“單詞”或“名稱”或“短語”。雖然區(qū)域管理可能需要也可能不需要“意義”作為注冊標準，但意義可能被證明是避免用戶混淆的有用工具。
Each IDL to be registered should be associated administratively with one or more languages.
每個要注冊的IDL都應(yīng)該在管理上與一種或多種語言相關(guān)聯(lián)。
Language associations should either be predetermined by the zone administrator and applied to the entire zone or be chosen by the registrants on a per-IDL basis. The latter may be necessary for some zones, but it will make administration more difficult and will increase the likelihood of conflicts in variant forms.
語言協(xié)會應(yīng)由區(qū)域管理員預先確定并應(yīng)用于整個區(qū)域，或由注冊人根據(jù)每個IDL選擇。對于某些區(qū)域，后者可能是必要的，但這將使管理更加困難，并增加各種形式?jīng)_突的可能性。
A given zone might have multiple languages associated with it or it may have no language specified at all. Omitting specification of a language may provide additional opportunities for user confusion and is therefore NOT recommended.
給定區(qū)域可能有多個與之關(guān)聯(lián)的語言，或者可能根本沒有指定語言。省略語言規(guī)范可能會給用戶帶來更多混淆的機會，因此不建議這樣做。
(b) Each language uses only a subset of Unicode characters. Therefore, if an IDL is associated with a language, it is not permitted to contain any Unicode character that is not within the valid subset for that language.
(b) 每種語言只使用Unicode字符的子集。因此，如果IDL與某種語言關(guān)聯(lián)，則不允許包含任何不在該語言有效子集內(nèi)的Unicode字符。
Each IDL to be registered must be verified against the valid subset of Unicode for the language(s) associated with the IDL.
必須根據(jù)與IDL關(guān)聯(lián)的語言的有效Unicode子集驗證要注冊的每個IDL。
That subset is specified by the list of characters appearing in the first column of the language and zone-specific tables as described later in this document.
該子集由出現(xiàn)在語言和區(qū)域特定表的第一列中的字符列表指定，如本文檔后面所述。
If the IDL fails this test for any of its associated languages, the IDL is not valid for registration.
如果IDL未通過任何相關(guān)語言的此測試，則IDL注冊無效。
Note that this verification is not necessarily linguistically accurate, because some languages have special rules. For example, some languages impose restrictions on the order in which particular combinations of characters may appear. Characters that are valid for the language, and hence permitted by this specification, might still not form valid words or even strings in the language.
注意，這種驗證在語言上不一定準確，因為有些語言有特殊的規(guī)則。例如，某些語言對特定字符組合的顯示順序施加限制。對于該語言有效的字符（因此本規(guī)范允許）可能仍然無法在該語言中形成有效的單詞甚至字符串。
(c) When an IDL is associated with a language, it may have Character Variants that depend on that language associated with it in addition to any Preferred Variants. These variants are potential sources of confusion with the Code Points in the original label string. Consequently, the labels generated from them should be unavailable to registrants of other names, words, or phrases.
(c) 當IDL與一種語言關(guān)聯(lián)時，除了任何首選變體之外，它還可能具有依賴于與之關(guān)聯(lián)的該語言的字符變體。這些變體可能會與原始標簽字符串中的代碼點混淆。因此，其他姓名、單詞或短語的注冊人不應(yīng)使用由其生成的標簽。
During registration, all labels generated from the Character Variants for the associated language(s) of the IDL should be reserved.
在注冊期間，應(yīng)保留從IDL關(guān)聯(lián)語言的字符變體生成的所有標簽。
IDL reservations of the type described here normally do not appear in the distributed DNS zone file. In other words, these reserved IDLs may not resolve. Domain name holders could request that these reserved IDLs be placed in the zone file and made active and resolvable.
此處所述類型的IDL保留通常不會出現(xiàn)在分布式DNS區(qū)域文件中。換句話說，這些保留的IDL可能無法解析。域名持有者可以請求將這些保留IDL放入?yún)^(qū)域文件中，并使其處于活動狀態(tài)和可解析狀態(tài)。
Zones will need to establish local policies about how they are to be made active. Specifically, many zones, especially at the top level, have prohibited or restricted the use of "CNAME"s DNS aliases, especially CNAMEs that point to nameserver delegation records (NS records). And long-term use of long-term aliases for domain hierarchies, rather than single names ("DNAME records") are considered problematic because of the recursion they can introduce into DNS lookups.
區(qū)域?qū)⑿枰贫P(guān)于如何使其活躍的地方政策。具體而言，許多區(qū)域，特別是頂級區(qū)域，已禁止或限制使用“CNAME”的DNS別名，特別是指向名稱服務(wù)器委派記錄（NS記錄）的CNAME。長期使用域?qū)哟谓Y(jié)構(gòu)的長期別名，而不是單一名稱（“DNAME記錄”）被認為是有問題的，因為它們可以引入DNS查找中的遞歸。
(d) When an IDL is a "name", "word", or "phrase", it will have Character Variants depending on the associated language. Furthermore, one or more of those Character Variants will be used more often than others for linguistic, political, or other reasons.
(d) 當IDL是“名稱”、“單詞”或“短語”時，它將根據(jù)相關(guān)語言具有字符變體。此外，出于語言、政治或其他原因，這些字符變體中的一個或多個將比其他字符變體更頻繁地使用。
These more commonly used variants are distinguished from ordinary Character Variants and are known as Preferred Variant(s) for the particular language.
這些更常用的變體與普通字符變體不同，被稱為特定語言的首選變體。
To increase the likelihood of correct and predictable resolution of the IDN by end users, all labels generated from the Preferred Variants for the associated language(s) should be resolvable.
為了增加最終用戶正確和可預測的IDN解析的可能性，從相關(guān)語言的首選變體生成的所有標簽都應(yīng)該是可解析的。
In other words, the Preferred Variant Labels should appear in the distributed DNS zone file.
換句話說，首選變量標簽應(yīng)該出現(xiàn)在分布式DNS區(qū)域文件中。
(e) IDLs associated with one or more languages may have a large number of Character Variant Labels or Preferred Variant Labels. Some of these labels may include combinations of characters that are meaningless or invalid linguistically. It may therefore be appropriate for a zone to adopt procedures that include only linguistically acceptable labels in the IDL Package.
(e) 與一種或多種語言關(guān)聯(lián)的IDL可能有大量字符變體標簽或首選變體標簽。其中一些標簽可能包含在語言上無意義或無效的字符組合。因此，對于一個區(qū)域來說，采用僅在IDL包中包含語言上可接受的標簽的程序可能是合適的。
A zone administrator may impose additional rules and other processing activities to limit the number of Character Variant Labels or Preferred Variant Labels that are actually reserved or registered.
區(qū)域管理員可以實施附加規(guī)則和其他處理活動，以限制實際保留或注冊的字符變體標簽或首選變體標簽的數(shù)量。
These additional rules and other processing activities are based on policies and/or procedures imposed on a per-zone basis and therefore are not within the scope of this document. Such policies or procedures might be used, for example, to restrict the number of Preferred Variant Labels actually reserved or to prevent certain words from being registered at all.
這些附加規(guī)則和其他處理活動基于每個區(qū)域?qū)嵤┑恼吆?/span>/或程序，因此不在本文件的范圍內(nèi)。例如，可以使用此類策略或程序來限制實際保留的首選變體標簽的數(shù)量，或者根本不允許注冊某些單詞。
(f) There are some Character Variant Labels and Preferred Variant Labels that are associated with each IDL. These labels are considered "equivalent" to each another. To avoid confusion, they all should be assigned to a single domain name holder.
(f) 有一些字符變體標簽和首選變體標簽與每個IDL關(guān)聯(lián)。這些標簽被視為彼此“等效”。為了避免混淆，它們都應(yīng)該分配給一個域名持有者。
The IDL and its variant labels should be grouped together into a single atomic unit, known in this document as an "IDL Package".
IDL及其變體標簽應(yīng)組合成一個單一的原子單元，在本文檔中稱為“IDL包”。
The IDL Package is created upon registration and is atomic: Transfer and deletion of an IDL is performed on the IDL Package as a whole. That is, an IDL within the IDL Package may not be transferred or deleted individually; any re-registration, transfers, or other actions that impact the IDL should also affect the other variants.
IDL包在注冊時創(chuàng)建，并且是原子的：IDL的傳輸和刪除作為一個整體在IDL包上執(zhí)行。也就是說，IDL包中的IDL不能單獨傳輸或刪除；影響IDL的任何重新注冊、傳輸或其他操作也應(yīng)影響其他變體。
The name-conflict resolution policy associated with this zone could result in a conflict with the principle of IDL Package atomicity. In such a case, the policy must be defined to make the precedence clear.
與此區(qū)域關(guān)聯(lián)的名稱沖突解決策略可能導致與IDL包原子性原則沖突。在這種情況下，必須定義策略以明確優(yōu)先級。
3.2. Registration of IDL
3.2. IDL的注冊
To conform to the principles described in 3.1, this document introduces two concepts: the Language Variant Table and the IDL Package. These are described in the next two subsections, followed by a description of the algorithm that is used to interpret the table and generate variant labels.
為了符合3.1中描述的原則，本文引入了兩個概念：語言變量表和IDL包。在接下來的兩個小節(jié)中對這些進行了描述，然后介紹了用于解釋表和生成變量標簽的算法。
3.2.1. Using the Language Variant Table
3.2.1. 使用語言變量表
For each zone that uses a given language, each language should have its own Language Variant Table. The table consists of a header section that identifies references and version information, followed by a section with one row for each Code Point that is valid for the language and three columns.
對于使用給定語言的每個區(qū)域，每種語言都應(yīng)該有自己的語言變體表。該表由一個標識引用和版本信息的標題部分組成，后面是一個部分，每個代碼點對應(yīng)一行（對該語言有效）和三列。
(1) The first column contains the subset of Unicode characters that is valid to be registered ("Valid Code Point"). This is used to verify the IDL to be registered (see 3.1b). As in the registration procedure described later, this column is used as an index to examine characters that appear in a proposed IDL to be processed. The collection of Valid Code Points in the table for a particular language can be thought of as defining the script for that language, although the normal definition of a script would not include, for example, ASCII characters with CJK ones.
(1) 第一列包含可有效注冊的Unicode字符子集（“有效代碼點”）。這用于驗證要注冊的IDL（見3.1b）。與后面描述的注冊過程一樣，此列用作索引，用于檢查要處理的建議IDL中出現(xiàn)的字符。表中特定語言的有效代碼點集合可被視為定義該語言的腳本，盡管腳本的正常定義不包括ASCII字符和CJK字符等。
(2) The second column contains the Preferred Variant(s) of the corresponding Unicode character in column one ("Valid Code Point"). These variant characters are used to generate the Preferred Variant Labels for the IDL. Those labels should be resolvable (see 3.1d). Under normal circumstances, all of those Preferred Variant Labels will be activated in the relevant zone file so that they will resolve when the DNS is queried for them.
(2) 第二列包含第一列中相應(yīng)Unicode字符的首選變體（“有效代碼點”）。這些變體字符用于生成IDL的首選變體標簽。這些標簽應(yīng)是可解析的（見3.1d）。在正常情況下，所有這些首選變量標簽將在相關(guān)區(qū)域文件中激活，以便在查詢DNS時解析它們。
(3) The third column contains the Character Variant(s) for the corresponding Valid Code Point. These are used to generate the Character Variant Labels of the IDL, which are then to be reserved (see 3.1c). Registration, or activation, of labels generated from Character Variants will normally be a registrant decision, subject to local policy.
(3) 第三列包含對應(yīng)有效代碼點的字符變量。這些用于生成IDL的字符變體標簽，然后保留這些標簽（見3.1c）。根據(jù)當?shù)卣?，注冊或激活由角色變體生成的標簽通常由注冊人決定。
Each entry in a column consists of one or more Code Points, expressed as a numeric character number in the Unicode table and optionally followed by a parenthetical reference. The first column, or Valid Code Point, may have only one Code Point specified in a given row. The other columns may have more than one.
列中的每個條目都由一個或多個代碼點組成，在Unicode表中表示為一個數(shù)字字符編號，并可選地后跟一個括號引用。第一列或有效代碼點在給定行中只能指定一個代碼點。其他列可能有多個。
Any row may be terminated with an optional comment, starting with "#".
任何行都可以以可選注釋結(jié)尾，以“#”開頭。
The formal syntax of the table and more-precise definitions of some of its organization appear in Section 5.
表的形式語法及其某些組織的更精確定義見第5節(jié)。
The Language Variant Table should be provided by a relevant group, organization, or body. However, the question of who is relevant or has the authority to create this table and the rules that define it is beyond the scope of this document.
語言變體表應(yīng)由相關(guān)團體、組織或機構(gòu)提供。但是，誰與此表相關(guān)或有權(quán)創(chuàng)建此表以及定義此表的規(guī)則的問題超出了本文件的范圍。
3.2.2. IDL Package
3.2.2. IDL包
The IDL Package is created on successful registration and consists of:
IDL包在成功注冊時創(chuàng)建，包括：
(1) the IDL registered
(1) IDL已注冊
(2) the language(s) associated with the IDL
(2) 與IDL關(guān)聯(lián)的語言
(3) the version of the associated character variant table
(3) 關(guān)聯(lián)字符變量表的版本
(4) the reserved IDLs
(4) 保留的IDL
(5) active IDLs, that is, "Zone Variant Labels" that are to appear in the DNS zone file
(5) 活動IDL，即將出現(xiàn)在DNS區(qū)域文件中的“區(qū)域變量標簽”
3.2.3. Procedure for Registering IDLs
3.2.3. 登記IDL的程序
An explanation follows each step.
每一步后面都有一個解釋。
Step 1. IN <= IDL to be registered and
{L} <= Set of languages associated with IN
Step 1. IN <= IDL to be registered and
{L} <= Set of languages associated with IN
Start the process with the label string (prospective IDL) to be registered and the associated language(s) as input.
以要注冊的標簽字符串（預期IDL）和關(guān)聯(lián)的語言作為輸入啟動流程。
Step 2. Generate the Nameprep-processed version of the IN, applying all mappings and canonicalization required by IDNA.
第二步。應(yīng)用IDNA所需的所有映射和規(guī)范化，生成中的Nameprep處理版本。
The prospective IDL is processed by using Nameprep to apply the normalizations and exclusions globally required to use IDNA. If the Nameprep processing fails, then the IDL is invalid and the registration process must stop.
通過使用Nameprep處理預期IDL，以在全球范圍內(nèi)應(yīng)用使用IDNA所需的規(guī)范化和排除。如果Nameprep處理失敗，則IDL無效，注冊過程必須停止。
Step 2.1. NP(IN) <= Nameprep processed IN Step 2.2. Check availability of NP(IN). If not available, route to conflict policy.
步驟2.1。NP（IN）<=步驟2.2中處理的Nameprep。檢查NP（IN）的可用性。如果不可用，請轉(zhuǎn)到?jīng)_突策略。
The Nameprep-processed IDL is then checked against the contents of the zone file and previously created IDL Packages. If it is already registered or reserved, then a conflict exists that must be resolved by applying whatever policy is applicable for the zone. For example, if FCFS is used, the registration process terminates unless the conflict resolution policy provides another alternative.
然后根據(jù)區(qū)域文件和先前創(chuàng)建的IDL包的內(nèi)容檢查Nameprep處理的IDL。如果已注冊或保留，則存在沖突，必須通過應(yīng)用適用于該區(qū)域的任何策略來解決。例如，如果使用FCFS，則注冊過程將終止，除非沖突解決策略提供了其他替代方案。
Step 3. Process each language. For each language (AL) in {L}
第三步。處理每種語言。對于{L}中的每種語言（AL）
Step 3 goes through all languages associated with the proposed IDL and checks each character (after Nameprep has been applied) for validity in each of them. It then applies the Preferred Variants (column 2 values) and the Character Variants (column 3 values) to generate candidate labels.
步驟3檢查與建議的IDL關(guān)聯(lián)的所有語言，并檢查每個字符（在應(yīng)用Nameprep之后）在每個字符中的有效性。然后應(yīng)用首選變量（第2列值）和字符變量（第3列值）生成候選標簽。
Step 3.1. Check validity of NP(IN) in AL. If failed, stop processing.
步驟3.1。檢查AL中NP（IN）的有效性。如果失敗，則停止處理。
In step 3.1, IDL validation is done by checking that every Code Point in the Nameprep-processed IDL is a Code Point allowed by the "Valid Code Point" column of the Character Variant Table for the language. This is then repeated for any other languages (and hence, Language Variant Tables) specified in the registration. If one or more Code Points are not valid, the registration process terminates.
在步驟3.1中，通過檢查Nameprep處理的IDL中的每個代碼點是否為該語言的字符變體表的“有效代碼點”列所允許的代碼點來完成IDL驗證。然后對注冊中指定的任何其他語言（因此，語言變體表）重復此操作。如果一個或多個代碼點無效，則注冊過程終止。
Step 3.2. PV(IN,AL) <= Set of available Nameprep-processed Preferred
Variants of NP(IN) in AL
Step 3.2. PV(IN,AL) <= Set of available Nameprep-processed Preferred
Variants of NP(IN) in AL
Step 3.2 generates the list of Preferred Variant Labels of the IDL by doing a combination (see Step 3.2A below) of all possible variants listed in the "Preferred Variant(s)" column for each Code Point in the Nameprep-processed IDL. The generated Preferred Variant Labels must be processed through Nameprep. If the Nameprep processing fails for any Preferred Variant Label (this is unlikely to occur if the Preferred Variants are processed through Nameprep before being placed in the table), then that variant label will be removed from the list. The remaining Preferred Variant Labels in the list are then checked to see whether they are already registered or reserved. If any are registered or reserved, then the conflict resolution policy will apply. In general, this will not prevent the originally requested IDL from being registered unless the policy prevents such registration. For example, if FCFS is applied, then the conflicting variants will be removed from the list, but the originally requested
步驟3.2通過對Nameprep處理的IDL中每個代碼點的“首選變量”列中列出的所有可能變量進行組合（參見下面的步驟3.2A），生成IDL首選變量標簽列表。必須通過Nameprep處理生成的首選變量標簽。如果任何首選變體標簽的Nameprep處理失敗（如果首選變體在放入表格之前通過Nameprep處理，則不太可能發(fā)生這種情況），則該變體標簽將從列表中刪除。然后檢查列表中剩余的首選變體標簽，查看它們是否已注冊或保留。如果已注冊或保留沖突解決策略，則將應(yīng)用沖突解決策略。通常，這不會阻止注冊最初請求的IDL，除非策略阻止此類注冊。例如，如果應(yīng)用了FCFS，則沖突變量將從列表中刪除，但最初請求的
IDL and any remaining variants will be registered (see steps 5 and 8 below).
將注冊IDL和任何其他變體（請參閱下面的步驟5和8）。
Step 3.2A Generating variant labels from Variant Code Points.
步驟3.2A從變體代碼點生成變體標簽。
Steps 3.2 and 3.3 require that the Preferred Variants and Character Variants be combined with the original IDL to form sets of variant labels. Conceptually, one starts with the original, Nameprep-processed, IDL and examines each of its characters in turn. If a character is encountered for which there is a corresponding Preferred Variant or Character Variant, a new variant label is produced with the Variant Code Point substituted for the original one. If variant labels already exist as the result of the processing of characters that appeared earlier in the original IDL, then the substitutions are made in them as well, resulting in additional generated variant labels. This operation is repeated separately for the Preferred Variants (in Step 3.2) and Character Variants (in Step 3.3). Of course, equivalent results could be achieved by processing the original IDL's characters in order, building the Preferred Variant Label set and Character Variant Label set in parallel.
步驟3.2和3.3要求首選變體和字符變體與原始IDL組合，以形成變體標簽集。從概念上講，我們從原始的Nameprep processed IDL開始，依次檢查它的每個字符。如果遇到具有相應(yīng)首選變體或字符變體的字符，將生成一個新的變體標簽，并用變體代碼點替換原始標簽。如果在處理原始IDL中較早出現(xiàn)的字符時，變體標簽已經(jīng)存在，那么也會在其中進行替換，從而生成額外的變體標簽。對于首選變體（步驟3.2）和字符變體（步驟3.3），分別重復此操作。當然，通過按順序處理原始IDL的字符，并行構(gòu)建首選變體標簽集和字符變體標簽集，可以獲得相同的結(jié)果。
This process will sometimes generate a very large number of labels. For example, if only two of the characters in the original IDL are associated with Preferred Variants and if the first of those characters has three Preferred Variants and the second has two, one ends up with 12 variant labels to be placed in the IDL Package and, normally, in the zone file. Repeating the process for Character Variants, if any exist, would further increase the number of labels. And if more than one language is specified for the original IDL, then repetition of the process for additional languages (see step 4, below) might further increase the size of the set.
此過程有時會生成大量標簽。例如，如果原始IDL中只有兩個字符與首選變體相關(guān)聯(lián)，并且其中第一個字符有三個首選變體，而第二個字符有兩個，則其中一個字符最后會有12個變體標簽，以放置在IDL包中，通常情況下，放置在區(qū)域文件中。對字符變體（如果存在）重復該過程將進一步增加標簽的數(shù)量。如果為原始IDL指定了多個語言，那么對其他語言重復該過程（參見下面的步驟4）可能會進一步增加集合的大小。
For illustrative purposes, the "combination" process could be achieved by a recursive function similar to the following pseudocode:
出于說明目的，“組合”過程可通過類似于以下偽代碼的遞歸函數(shù)實現(xiàn)：
Function Combination(Str)
F <= first codepoint of Str
SStr <= Substring of Str, without the first code point
NSC <= {}
Function Combination(Str)
F <= first codepoint of Str
SStr <= Substring of Str, without the first code point
NSC <= {}
If SStr is empty then for each V in (Variants of code point F) NSC = NSC set-union (the string with the code point V) End of Loop Else SubCom = Combination(SStr) For each V in (Variants of code point F) For each SC in SubCom NSC = NSC set-union (the string with the first code point V followed by the string SC) End of Loop End of Loop Endif
如果SStr為空，則對于每個V in（代碼點F的變體）NSC=NSC集合并集（帶代碼點V的字符串）循環(huán)結(jié)束Else SubCom=組合（SStr）對于每個V in（代碼點F的變體）SubCom中的每個SC NSC=NSC集合并集（帶第一個代碼點V的字符串后跟字符串SC）循環(huán)結(jié)束循環(huán)結(jié)束Endif
Return NSC
返回NSC
Step 3.3. CV(IN,AL) <= Set of available Nameprep-processed Character
Variants of NP(IN) in AL
Step 3.3. CV(IN,AL) <= Set of available Nameprep-processed Character
Variants of NP(IN) in AL
This step generates the list of Character Variant Labels by doing a combination (see Step 3.2A above) of all the possible variants listed in the "Character Variant(s)" column for each Code Point in the Nameprep-processed original IDL. As with the Preferred Variant Labels, the generated Character Variant Labels must be processed by, and acceptable to, Nameprep. If the Nameprep processing fails for a Character Variant Label, then that variant label will be removed from the list. The remaining Character Variant Labels are then checked to be sure they are not registered or reserved. If one or more are, then the conflict resolution policy is applied. As with Preferred Variant Labels, a conflict that is resolved in favor of the earlier registrant does not, in general, prevent the IDL from being registered, nor the remaining variants from being reserved in step 6 below.
此步驟通過對Nameprep處理的原始IDL中每個代碼點的“字符變體”列中列出的所有可能變體進行組合（請參見上面的步驟3.2A），生成字符變體標簽列表。與首選變體標簽一樣，生成的字符變體標簽必須由Nameprep處理并為其接受。如果字符變體標簽的Nameprep處理失敗，則該變體標簽將從列表中刪除。然后檢查其余的字符變體標簽，以確保它們未注冊或保留。如果存在一個或多個沖突，則應(yīng)用沖突解決策略。與首選變體標簽一樣，解決有利于早期注冊人的沖突通常不會阻止IDL注冊，也不會阻止在下面的步驟6中保留其余變體。
Step 3.4. End of Loop
步驟3.4。循環(huán)結(jié)束
Step 4. Let PVall be the set-union of all PV(IN,AL)
第四步。設(shè)PVall為所有PV（IN，AL）的集合并集
Step 4 generates the Preferred Variants Label for all languages. In this step, and again in step 6 below, the zone administrator may impose additional rules and processing activities to restrict the number of Preferred (tentatively to be reserved and activated) and Character (tentatively to be reserved) Label Variants. These additional rules and processing activities are zone policy specific and therefore are not specified in this document.
步驟4為所有語言生成首選變體標簽。在這一步中，以及在下面的第6步中，區(qū)域管理員可以實施附加規(guī)則和處理活動，以限制首選（暫定保留和激活）和字符（暫定保留）標簽變體的數(shù)量。這些附加規(guī)則和處理活動是特定于區(qū)域策略的，因此未在本文檔中指定。
Step 5. {ZV} <= PVall set-union NP(IN)
Step 5. {ZV} <= PVall set-union NP(IN)
Step 5 generates the initial Zone Variants. The set includes all Preferred Variants for all languages and the original Nameprep-processed IDL. Unless excluded by further processing, these Zone Variants will be activated. That is, placed into the DNS zone. Note that the "set-union" operation will eliminate any duplicates.
步驟5生成初始區(qū)域變量。該集合包括所有語言的所有首選變體以及原始Nameprep處理的IDL。除非通過進一步處理排除，否則這些區(qū)域變量將被激活。也就是說，放入DNS區(qū)域。請注意，“set union”操作將消除任何重復項。
Step 6. Let CVall be the set-union of all CV(IN,AL), set-minus {ZV}
第六步。設(shè)CVall是所有CV（IN，AL）的集合并集，集合減去{ZV}
Step 6 generates the Reserved Label Variants (the Character Variant Label set). These labels are normally reserved but not activated. The set includes all Character Variant Labels for all languages, but not the Zone Variants defined in the previous step. The set-union and set-minus operations eliminate any duplicates.
步驟6生成保留標簽變體（字符變體標簽集）。這些標簽通常保留但未激活。該集合包括所有語言的所有字符變體標簽，但不包括上一步中定義的區(qū)域變體。集合并集和集合減號操作可消除任何重復項。
Step 7. Create IDL Package for IN using IN, {L}, {ZV} and CVall
Step 7. Create IDL Package for IN using IN, {L}, {ZV} and CVall
In Step 7, the "IDL Package" is created using the original IDL, the associated language(s), the Zone Variant Labels, and the Reserved Variant Labels. If zone-specific additional processing or filtering is to be applied to eliminate linguistically inappropriate or other forms, it should be applied before the IDL Package is actually assembled.
在步驟7中，使用原始IDL、關(guān)聯(lián)語言、區(qū)域變量標簽和保留變量標簽創(chuàng)建“IDL包”。如果要應(yīng)用特定于區(qū)域的附加處理或過濾來消除語言上不合適的形式或其他形式，則應(yīng)在實際組裝IDL包之前應(yīng)用。
Step 8. Put {ZV} into zone file
第八步。將{ZV}放入?yún)^(qū)域文件
The activated IDLs are converted via ToASCII with UseSTD13ASCIIRules [IDNA] before being placed into the zone file. This conversion results in the IDLs being in the actual IDNA ("Punycode") form used in zone files, while the IDLs have been carried in Unicode form up to this point. If ToASCII fails for any of the activated IDLs, that IDL must not be placed into the zone file. If the IDL is a subdomain name, it will be delegated.
激活的IDL在放入?yún)^(qū)域文件之前通過ToASCII和UseSTD13ASCIIRules[IDNA]進行轉(zhuǎn)換。這種轉(zhuǎn)換導致IDL采用區(qū)域文件中使用的實際IDNA（“Punycode”）形式，而到目前為止，IDL一直采用Unicode形式。如果任何激活的IDL的ToASCII失敗，則不得將該IDL放入?yún)^(qū)域文件中。如果IDL是一個子域名，它將被委派。
3.3. Deletion and Transfer of IDL and IDL Package
3.3. IDL和IDL包的刪除和傳輸
In traditional domain administration, every Domain Name Label is independent of all other Domain Name Labels. Registration, deletion, and transfer of labels is done on a per-label basis. However, with the guidelines discussed here, each IDL is associated with specific languages, with all label variants, both active (zone) and reserved, together in an IDL Package. This quite deliberately prohibits labels that contain sufficient mixtures of characters from different scripts to make them impossible as words in any given language. If a zone chooses to not impose that restriction--that is, to permit labels to be constructed by picking characters from several different languages and scripts--then the guidelines described here would be inappropriate.
在傳統(tǒng)的域管理中，每個域名標簽都獨立于所有其他域名標簽。標簽的注冊、刪除和轉(zhuǎn)移按標簽進行。然而，根據(jù)這里討論的指導原則，每個IDL都與特定的語言相關(guān)聯(lián)，所有標簽變體（活動（區(qū)域）和保留）都在一個IDL包中。這相當有意地禁止標簽包含來自不同腳本的足夠多的字符混合，使它們不可能成為任何給定語言中的單詞。如果一個區(qū)域選擇不施加這種限制——也就是說，允許通過從幾種不同的語言和腳本中選取字符來構(gòu)造標簽——那么這里描述的準則將是不合適的。
As stated earlier, the IDL package should be treated as a single atomic unit and all variants of the IDL should belong to a single domain-name holder. If the local policy related to the handling of disagreements requires a particular IDL to be transferred and deleted independently of the IDL Package, the conflict policy would take precedence. In such an event, the conflict policy should include a transfer or delete procedure that takes the nature of IDL Packages into consideration.
如前所述，IDL包應(yīng)被視為單個原子單元，IDL的所有變體應(yīng)屬于單個域名持有者。如果與處理分歧相關(guān)的本地政策要求獨立于IDL包傳輸和刪除特定IDL，則沖突政策將優(yōu)先。在這種情況下，沖突策略應(yīng)包括一個傳輸或刪除過程，該過程應(yīng)考慮IDL包的性質(zhì)。
When an IDL Package is deleted, all of the Zone and Reserved Label Variants again become available. The deletion of one IDL Package does not change any other IDL Packages.
刪除IDL包后，所有分區(qū)和保留標簽變體將再次可用。刪除一個IDL包不會更改任何其他IDL包。
3.4. Activation and Deactivation of IDL variants
3.4. IDL變體的激活和停用
Because there are active (registered) IDLs and inactive (reserved but not registered) IDLs within an IDL package, processes are required to activate or deactivate IDL variants within an IDL Package.
由于IDL包中存在活動（已注冊）IDL和非活動（保留但未注冊）IDL，因此需要流程來激活或停用IDL包中的IDL變體。
3.4.1. Activation Algorithm
3.4.1. 激活算法
Step 1. IN <= IDL to be activated and PA <= IDL Package
Step 1. IN <= IDL to be activated and PA <= IDL Package
Start with the IDL to be activated and the IDL Package of which it is a member.
從要激活的IDL及其所屬的IDL包開始。
Step 2. NP(IN) <= Nameprep processed IN
Step 2. NP(IN) <= Nameprep processed IN
Process the IDL through Nameprep. This step should never cause a problem, or even a change, since all labels that become part of the IDL Package are processed through Nameprep in Step 3.2 or 3.3 of the Registration procedure (section 3.2.3).
通過Nameprep處理IDL。此步驟不應(yīng)引起問題，甚至不應(yīng)引起更改，因為成為IDL包一部分的所有標簽都是通過注冊程序（第3.2.3節(jié)）步驟3.2或3.3中的Nameprep處理的。
Step 3. If NP(IN) not in CVall then stop
第三步。如果NP（IN）不在CVall中，則停止
Verify that the Nameprep-processed version of the IDL appears as a still-unactivated label in the IDL Package, i.e., in the list of Reserved Label Variants, CVall. It might be a useful "sanity check" to also verify that it does not already appear in the zone file.
驗證Nameprep處理過的IDL版本是否在IDL包中顯示為仍然未激活的標簽，即在保留標簽變體列表CVall中。這可能是一個有用的“健全性檢查”，還可以驗證它是否已經(jīng)出現(xiàn)在區(qū)域文件中。
Step 4. CVall <= CVall set-minus NP(IN) and {ZV} <= {ZV} set-union
NP(IN)
Step 4. CVall <= CVall set-minus NP(IN) and {ZV} <= {ZV} set-union
NP(IN)
Within the IDL Package, remove the Nameprep-processed version of the IDL from the list of Reserved Label Variants and add it to the list of active (zone) label variants.
在IDL包中，從保留標簽變體列表中刪除Nameprep處理過的IDL版本，并將其添加到活動（區(qū)域）標簽變體列表中。
Step 5. Put {ZV} into the zone file
第五步。將{ZV}放入?yún)^(qū)域文件
Actually register (activate) the Zone Variant Labels.
實際注冊（激活）區(qū)域變量標簽。
3.4.2. Deactivation Algorithm
3.4.2. 去激活算法
Step 1. IN <= IDL to be deactivated and PA <= IDL Package
Step 1. IN <= IDL to be deactivated and PA <= IDL Package
As with activation, start with the IDL to be deactivated and the IDL Package of which it is a member.
與激活一樣，從要停用的IDL及其所屬的IDL包開始。
Step 2. NP(IN) <= Nameprep processed IN
Step 2. NP(IN) <= Nameprep processed IN
Get the Nameprep-processed version of the name (see discussion in the previous section).
獲取名稱的Nameprep處理版本（請參閱上一節(jié)中的討論）。
Step 3. If NP(IN) not in {ZV} then stop
Step 3. If NP(IN) not in {ZV} then stop
Verify that the Nameprep-processed version of the IDL appears as an activated (zone) label variant in the IDL Package. It might be a useful "sanity check" at this point to also verify that it actually appears in the zone file.
驗證Nameprep處理過的IDL版本在IDL包中是否顯示為激活（區(qū)域）標簽變體。在這一點上，它可能是一個有用的“健全性檢查”，以驗證它是否確實出現(xiàn)在區(qū)域文件中。
Step 4. CVall <= CVall set-union NP(IN) and {ZV} <= {ZV} set-minus
NP(IN)
Step 4. CVall <= CVall set-union NP(IN) and {ZV} <= {ZV} set-minus
NP(IN)
Within the IDL Package, remove the Nameprep-processed version of the IDL from the list of Active (Zone) Label Variants and add it to the list of Reserved (but inactive) Label Variants.
在IDL包中，從活動（區(qū)域）標簽變體列表中刪除Nameprep處理過的IDL版本，并將其添加到保留（但非活動）標簽變體列表中。
Step 5. Put {ZV} into the zone file
第五步。將{ZV}放入?yún)^(qū)域文件
3.5. Managing Changes in Language Associations
3.5. 管理語言協(xié)會的變化
Since the IDL package is an atomic unit and the associated list of variants must not be changed after creation, this document does not include a mechanism for adding and deleting language associations within the IDL package. Instead, it recommends deleting the IDL package entirely, followed by a registration with the new set of languages. Zone administrators may find it desirable to devise procedures that prevent other parties from capturing the labels in the IDL Package during these operations.
由于IDL包是一個原子單元，創(chuàng)建后不得更改相關(guān)的變體列表，因此本文檔不包括在IDL包中添加和刪除語言關(guān)聯(lián)的機制。相反，它建議完全刪除IDL包，然后注冊新的語言集。區(qū)域管理員可能會發(fā)現(xiàn)，需要設(shè)計一些程序，防止其他方在這些操作期間捕獲IDL包中的標簽。
3.6. Managing Changes to the Language Variant Tables
3.6. 管理語言變量表的更改
Language Variant Tables are subject to changes over time, and these changes may or may not be backward compatible. It is possible that updated Language Variant Tables may produce a different set of Preferred Variants and Reserved Variants.
語言變量表會隨著時間的推移而發(fā)生變化，這些變化可能向后兼容，也可能不向后兼容。更新后的語言變體表可能會產(chǎn)生一組不同的首選變體和保留變體。
In order to preserve the atomicity of the IDL Package, when the Language Variant Table is changed, IDL Packages created using the previous version of the Language Variant Table must not be updated or affected.
為了保持IDL包的原子性，當語言變量表發(fā)生更改時，不得更新或影響使用以前版本的語言變量表創(chuàng)建的IDL包。
4. Examples of Guideline Use in Zones
4. 區(qū)域中使用指南的示例
To provide a meaningful example, some Language Variant Tables must be defined. Assume, then, for the purpose of giving examples, that the following four Language Variant Tables are defined:
為了提供一個有意義的示例，必須定義一些語言變量表。為了舉例，假設(shè)定義了以下四種語言變體表：
Note: these tables are not a representation of the actual tables, and they do not contain sufficient entries to be used in any actual implementation. IANA maintains a voluntary registry of actual tables [IANA-LVTABLES] which may be consulted for complete examples.
注意：這些表不是實際表的表示，并且它們不包含足夠的條目，無法在任何實際實現(xiàn)中使用。IANA維護一個實際表的自愿登記冊[IANA-LVTABLES]，完整示例可參考該登記冊。
a) Language Variant Table for zh-cn and zh-sg
a) zh cn和zh sg的語言變量表
Reference 1 CP936 (commonly known as GBK) Reference 2 zVariant, zTradVariant, zSimpVariant in Unihan.txt [UNIHAN] Reference 3 List of Simplified character Table (Simplified column) Reference 4 zSimpVariant in Unihan.txt [UNIHAN] Reference 5 variant that exists in GB2312, common simplified hanzi
參考文獻1 CP936（俗稱GBK）參考文獻2 Unihan.txt中的zVariant、zTradVariant、zSimpVariant[Unihan]參考文獻3簡化字符表列表（簡化列）參考文獻4 Unihan.txt中的zSimpVariant[Unihan]參考文獻5 GB2312中存在的變體，通用簡化漢字
Version 1 20020701 # July 2002
版本1 20020701#2002年7月
56E2(1);56E2(5);5718(2) # sphere, ball, circle; mass, lump
5718(1);56E2(4);56E2(2),56E3(2) # sphere, ball, circle; mass, lump
60F3(1);60F3(5); # think, speculate, plan, consider
654E(1);6559(5);6559(2) # teach
56E2(1);56E2(5);5718(2) # sphere, ball, circle; mass, lump
5718(1);56E2(4);56E2(2),56E3(2) # sphere, ball, circle; mass, lump
60F3(1);60F3(5); # think, speculate, plan, consider
654E(1);6559(5);6559(2) # teach
6559(1);6559(5);654E(2) # teach, class
6DF8(1);6E05(5);6E05(2) # clear
6E05(1);6E05(5);6DF8(2) # clear, pure, clean; peaceful
771E(1);771F(5);771F(2) # real, actual, true, genuine
771F(1);771F(5);771E(2) # real, actual, true, genuine
8054(1);8054(3);806F(2) # connect, join; associate, ally
806F(1);8054(3);8054(2),8068(2) # connect, join; associate, ally
96C6(1);96C6(5); # assemble, collect together
6559(1);6559(5);654E(2) # teach, class
6DF8(1);6E05(5);6E05(2) # clear
6E05(1);6E05(5);6DF8(2) # clear, pure, clean; peaceful
771E(1);771F(5);771F(2) # real, actual, true, genuine
771F(1);771F(5);771E(2) # real, actual, true, genuine
8054(1);8054(3);806F(2) # connect, join; associate, ally
806F(1);8054(3);8054(2),8068(2) # connect, join; associate, ally
96C6(1);96C6(5); # assemble, collect together
b) Language Variant Table for zh-tw
b) zh tw的語言變量表
Reference 1 CP950 (commonly known as BIG5) Reference 2 zVariant, zTradVariant, zSimpVariant in Unihan.txt Reference 3 List of Simplified Character Table (Traditional column) Reference 4 zTradVariant in Unihan.txt
參考1 CP950（通常稱為BIG5）參考2 Unihan.txt中的zVariant、zTradVariant、zSimpVariant參考3簡化字符表列表（傳統(tǒng)列）參考4 Unihan.txt中的zTradVariant
Version 1 20020701 # July 2002
版本1 20020701#2002年7月
5718(1);5718(4);56E2(2),56E3(2) # sphere, ball, circle; mass, lump
60F3(1);60F3(1); # think, speculate, plan, consider
6559(1);6559(1);654E(2) # teach, class
6E05(1);6E05(1);6DF8(2) # clear, pure, clean; peaceful
771F(1);771F(1);771E(2) # real, actual, true, genuine
806F(1);806F(3);8054(2),8068(2) # connect, join; associate, ally
96C6(1);96C6(1); # assemble, collect together
5718(1);5718(4);56E2(2),56E3(2) # sphere, ball, circle; mass, lump
60F3(1);60F3(1); # think, speculate, plan, consider
6559(1);6559(1);654E(2) # teach, class
6E05(1);6E05(1);6DF8(2) # clear, pure, clean; peaceful
771F(1);771F(1);771E(2) # real, actual, true, genuine
806F(1);806F(3);8054(2),8068(2) # connect, join; associate, ally
96C6(1);96C6(1); # assemble, collect together
c) Language Variant Table for ja
c) ja語言變量表
Reference 1 CP932 (commonly known as Shift-JIS) Reference 2 zVariant in Unihan.txt Reference 3 variant that exists in JIS X0208, commonly used Kanji
參考文獻1 CP932（通常稱為Shift JIS）參考文獻2 Unihan.txt參考文獻3變體中的zVariant存在于JIS X0208中，常用漢字
Version 1 20020701 # July 2002
版本1 20020701#2002年7月
5718(1);5718(3);56E3(2) # sphere, ball, circle; mass, lump
60F3(1);60F3(3); # think, speculate, plan, consider
654E(1);6559(3);6559(2) # teach
6559(1);6559(3);654E(2) # teach, class
6DF8(1);6E05(3);6E05(2) # clear
6E05(1);6E05(3);6DF8(2) # clear, pure, clean; peaceful
771E(1);771E(1);771F(2) # real, actual, true, genuine
771F(1);771F(1);771E(2) # real, actual, true, genuine
806F(1);806F(1);8068(2) # connect, join; associate, ally
96C6(1);96C6(3); # assemble, collect together
5718(1);5718(3);56E3(2) # sphere, ball, circle; mass, lump
60F3(1);60F3(3); # think, speculate, plan, consider
654E(1);6559(3);6559(2) # teach
6559(1);6559(3);654E(2) # teach, class
6DF8(1);6E05(3);6E05(2) # clear
6E05(1);6E05(3);6DF8(2) # clear, pure, clean; peaceful
771E(1);771E(1);771F(2) # real, actual, true, genuine
771F(1);771F(1);771E(2) # real, actual, true, genuine
806F(1);806F(1);8068(2) # connect, join; associate, ally
96C6(1);96C6(3); # assemble, collect together
d) Language Variant Table for ko
d) ko語言變體表
Reference 1 CP949 (commonly known as EUC-KR)
參考文獻1 CP949（通常稱為EUC-KR）
Reference 2 zVariant and K-source in Unihan.txt
Unihan.txt中的參考2 zVariant和K源
Version 1 20020701 # July 2002
版本1 20020701#2002年7月
5718(1);5718(1);56E3(2) # sphere, ball, circle; mass, lump
60F3(1);60F3(1); # think, speculate, plan, consider
654E(1);654E(1);6559(2) # teach
6DF8(1);6DF8(1);6E05(2) # clear
771E(1);771E(1);771F(2) # real, actual, true, genuine
806F(1);806F(1);8068(2) # connect, join; associate, ally
96C6(1);96C6(1); # assemble, collect together
5718(1);5718(1);56E3(2) # sphere, ball, circle; mass, lump
60F3(1);60F3(1); # think, speculate, plan, consider
654E(1);654E(1);6559(2) # teach
6DF8(1);6DF8(1);6E05(2) # clear
771E(1);771E(1);771F(2) # real, actual, true, genuine
806F(1);806F(1);8068(2) # connect, join; associate, ally
96C6(1);96C6(1); # assemble, collect together
Example 1: IDL = (U+6E05 U+771F U+6559) *qing2 zhen1 jiao4*
{L} = {zh-cn, zh-sg, zh-tw}
Example 1: IDL = (U+6E05 U+771F U+6559) *qing2 zhen1 jiao4*
{L} = {zh-cn, zh-sg, zh-tw}
NP(IN) = (U+6E05 U+771F U+6559)
PV(IN,zh-cn) = (U+6E05 U+771F U+6559)
PV(IN,zh-sg) = (U+6E05 U+771F U+6559)
PV(IN,zh-tw) = (U+6E05 U+771F U+6559)
NP(IN) = (U+6E05 U+771F U+6559)
PV(IN,zh-cn) = (U+6E05 U+771F U+6559)
PV(IN,zh-sg) = (U+6E05 U+771F U+6559)
PV(IN,zh-tw) = (U+6E05 U+771F U+6559)
{ZV} = {(U+6E05 U+771F U+6559)}
CVall = {(U+6E05 U+771E U+6559),
(U+6E05 U+771E U+654E),
(U+6E05 U+771F U+654E),
(U+6DF8 U+771E U+6559),
(U+6DF8 U+771E U+654E),
(U+6DF8 U+771F U+6559),
(U+6DF8 U+771F U+654E)}
{ZV} = {(U+6E05 U+771F U+6559)}
CVall = {(U+6E05 U+771E U+6559),
(U+6E05 U+771E U+654E),
(U+6E05 U+771F U+654E),
(U+6DF8 U+771E U+6559),
(U+6DF8 U+771E U+654E),
(U+6DF8 U+771F U+6559),
(U+6DF8 U+771F U+654E)}
Example 2: IDL = (U+6E05 U+771F U+6559) *qing2 zhen1 jiao4*
{L} = {ja}
Example 2: IDL = (U+6E05 U+771F U+6559) *qing2 zhen1 jiao4*
{L} = {ja}
NP(IN) = (U+6E05 U+771F U+6559)
PV(IN,ja) = (U+6E05 U+771F U+6559)
{ZV} = {(U+6E05 U+771F U+6559)}
NP(IN) = (U+6E05 U+771F U+6559)
PV(IN,ja) = (U+6E05 U+771F U+6559)
{ZV} = {(U+6E05 U+771F U+6559)}
CVall = {(U+6E05 U+771E U+6559),
(U+6E05 U+771E U+654E),
(U+6E05 U+771F U+654E),
(U+6DF8 U+771E U+6559),
(U+6DF8 U+771E U+654E),
(U+6DF8 U+771F U+6559),
(U+6DF8 U+771F U+654E)}
CVall = {(U+6E05 U+771E U+6559),
(U+6E05 U+771E U+654E),
(U+6E05 U+771F U+654E),
(U+6DF8 U+771E U+6559),
(U+6DF8 U+771E U+654E),
(U+6DF8 U+771F U+6559),
(U+6DF8 U+771F U+654E)}
Example 3: IDL = (U+6E05 U+771F U+6559) *qing2 zhen1 jiao4*
{L} = {zh-cn, zh-sg, zh-tw, ja, ko}
Example 3: IDL = (U+6E05 U+771F U+6559) *qing2 zhen1 jiao4*
{L} = {zh-cn, zh-sg, zh-tw, ja, ko}
NP(IN) = (U+6E05 U+771F U+6559) *qing2 zhen1 jiao4*
NP(IN) = (U+6E05 U+771F U+6559) *qing2 zhen1 jiao4*
Invalid registration because U+6E05 is invalid in L = ko
注冊無效，因為U+6E05在L=ko中無效
Example 4: IDL = (U+806F U+60F3 U+96C6 U+5718)
*lian2 xiang3 ji2 tuan2*
{L} = {zh-cn, zh-sg, zh-tw}
Example 4: IDL = (U+806F U+60F3 U+96C6 U+5718)
*lian2 xiang3 ji2 tuan2*
{L} = {zh-cn, zh-sg, zh-tw}
NP(IN) = (U+806F U+60F3 U+96C6 U+5718)
PV(IN,zh-cn) = (U+8054 U+60F3 U+96C6 U+56E2)
PV(IN,zh-sg) = (U+8054 U+60F3 U+96C6 U+56E2)
PV(IN,zh-tw) = (U+806F U+60F3 U+96C6 U+5718)
{ZV} = {(U+8054 U+60F3 U+96C6 U+56E2),
(U+806F U+60F3 U+96C6 U+5718)}
CVall = {(U+8054 U+60F3 U+96C6 U+56E3),
(U+8054 U+60F3 U+96C6 U+5718),
(U+806F U+60F3 U+96C6 U+56E2),
(U+806f U+60F3 U+96C6 U+56E3),
(U+8068 U+60F3 U+96C6 U+56E2),
(U+8068 U+60F3 U+96C6 U+56E3),
(U+8068 U+60F3 U+96C6 U+5718)
NP(IN) = (U+806F U+60F3 U+96C6 U+5718)
PV(IN,zh-cn) = (U+8054 U+60F3 U+96C6 U+56E2)
PV(IN,zh-sg) = (U+8054 U+60F3 U+96C6 U+56E2)
PV(IN,zh-tw) = (U+806F U+60F3 U+96C6 U+5718)
{ZV} = {(U+8054 U+60F3 U+96C6 U+56E2),
(U+806F U+60F3 U+96C6 U+5718)}
CVall = {(U+8054 U+60F3 U+96C6 U+56E3),
(U+8054 U+60F3 U+96C6 U+5718),
(U+806F U+60F3 U+96C6 U+56E2),
(U+806f U+60F3 U+96C6 U+56E3),
(U+8068 U+60F3 U+96C6 U+56E2),
(U+8068 U+60F3 U+96C6 U+56E3),
(U+8068 U+60F3 U+96C6 U+5718)
Example 5: IDL = (U+8054 U+60F3 U+96C6 U+56E2)
*lian2 xiang3 ji2 tuan2*
{L} = {zh-cn, zh-sg}
Example 5: IDL = (U+8054 U+60F3 U+96C6 U+56E2)
*lian2 xiang3 ji2 tuan2*
{L} = {zh-cn, zh-sg}
NP(IN) = (U+8054 U+60F3 U+96C6 U+56E2)
PV(IN,zh-cn) = (U+8054 U+60F3 U+96C6 U+56E2)
PV(IN,zh-sg) = (U+8054 U+60F3 U+96C6 U+56E2)
{ZV} = {(U+8054 U+60F3 U+96C6 U+56E2)}
CVall = {(U+8054 U+60F3 U+96C6 U+56E3),
(U+8054 U+60F3 U+96C6 U+5718),
(U+806F U+60F3 U+96C6 U+56E2),
(U+806f U+60F3 U+96C6 U+56E3),
(U+806F U+60F3 U+96C6 U+5718),
(U+8068 U+60F3 U+96C6 U+56E2),
(U+8068 U+60F3 U+96C6 U+56E3),
(U+8068 U+60F3 U+96C6 U+5718)}
NP(IN) = (U+8054 U+60F3 U+96C6 U+56E2)
PV(IN,zh-cn) = (U+8054 U+60F3 U+96C6 U+56E2)
PV(IN,zh-sg) = (U+8054 U+60F3 U+96C6 U+56E2)
{ZV} = {(U+8054 U+60F3 U+96C6 U+56E2)}
CVall = {(U+8054 U+60F3 U+96C6 U+56E3),
(U+8054 U+60F3 U+96C6 U+5718),
(U+806F U+60F3 U+96C6 U+56E2),
(U+806f U+60F3 U+96C6 U+56E3),
(U+806F U+60F3 U+96C6 U+5718),
(U+8068 U+60F3 U+96C6 U+56E2),
(U+8068 U+60F3 U+96C6 U+56E3),
(U+8068 U+60F3 U+96C6 U+5718)}
Example 6: IDL = (U+8054 U+60F3 U+96C6 U+56E2)
*lian2 xiang3 ji2 tuan2*
{L} = {zh-cn, zh-sg, zh-tw}
Example 6: IDL = (U+8054 U+60F3 U+96C6 U+56E2)
*lian2 xiang3 ji2 tuan2*
{L} = {zh-cn, zh-sg, zh-tw}
NP(IN) = (U+8054 U+60F3 U+96C6 U+56E2)
Invalid registration because U+8054 is invalid in L = zh-tw
NP(IN) = (U+8054 U+60F3 U+96C6 U+56E2)
Invalid registration because U+8054 is invalid in L = zh-tw
Example 7: IDL = (U+806F U+60F3 U+96C6 U+5718)
*lian2 xiang3 ji2 tuan2*
{L} = {ja,ko}
Example 7: IDL = (U+806F U+60F3 U+96C6 U+5718)
*lian2 xiang3 ji2 tuan2*
{L} = {ja,ko}
NP(IN) = (U+806F U+60F3 U+96C6 U+5718)
PV(IN,ja) = (U+806F U+60F3 U+96C6 U+5718)
PV(IN,ko) = (U+806F U+60F3 U+96C6 U+5718)
{ZV} = {(U+806F U+60F3 U+96C6 U+5718)}
NP(IN) = (U+806F U+60F3 U+96C6 U+5718)
PV(IN,ja) = (U+806F U+60F3 U+96C6 U+5718)
PV(IN,ko) = (U+806F U+60F3 U+96C6 U+5718)
{ZV} = {(U+806F U+60F3 U+96C6 U+5718)}
CVall = {(U+806F U+60F3 U+96C6 U+56E3),
(U+8068 U+60F3 U+96C6 U+5718),
(U+8068 U+60F3 U+96C6 U+56E3)}
CVall = {(U+806F U+60F3 U+96C6 U+56E3),
(U+8068 U+60F3 U+96C6 U+5718),
(U+8068 U+60F3 U+96C6 U+56E3)}
5. Syntax Description for the Language Variant Table
5. 語言變量表的語法說明
The formal syntax for the Language Variant Table is as follows, using the IETF "ABNF" metalanguage [ABNF]. Some comments on this syntax appear immediately after it.
語言變量表的形式語法如下，使用IETF“ABNF”元語言[ABNF]。關(guān)于此語法的一些注釋會立即出現(xiàn)在后面。
5.1. ABNF Syntax
5.1. ABNF語法
LanguageVariantTable = 1*ReferenceLine VersionLine 1*EntryLine
ReferenceLine = "Reference" SP RefNo SP RefDesciption [ Comment ] CRLF
RefNo = 1*DIGIT
RefDesciption = *[VCHAR]
VersionLine = "Version" SP VersionNo SP VersionDate [ Comment ] CRLF
VersionNo = 1*DIGIT
VersionDate = YYYYMMDD
EntryLine = VariantEntry/Comment CRLF
LanguageVariantTable = 1*ReferenceLine VersionLine 1*EntryLine
ReferenceLine = "Reference" SP RefNo SP RefDesciption [ Comment ] CRLF
RefNo = 1*DIGIT
RefDesciption = *[VCHAR]
VersionLine = "Version" SP VersionNo SP VersionDate [ Comment ] CRLF
VersionNo = 1*DIGIT
VersionDate = YYYYMMDD
EntryLine = VariantEntry/Comment CRLF
VariantEntry = ValidCodePoint ";"
PreferredVariant ";" CharacterVariant [ Comment ]
ValidCodePoint = CodePoint
RefList = RefNo 0*( "," RefNo )
PreferredVariant = CodePointSet 0*( "," CodePointSet )
CharacterVariant = CodePointSet 0*( "," CodePointSet )
CodePointSet = CodePoint 0*( SP CodePoint )
CodePoint = 4*8DIGIT [ "(" Reflist ")" ]
Comment = "#" *VCHAR
VariantEntry = ValidCodePoint ";"
PreferredVariant ";" CharacterVariant [ Comment ]
ValidCodePoint = CodePoint
RefList = RefNo 0*( "," RefNo )
PreferredVariant = CodePointSet 0*( "," CodePointSet )
CharacterVariant = CodePointSet 0*( "," CodePointSet )
CodePointSet = CodePoint 0*( SP CodePoint )
CodePoint = 4*8DIGIT [ "(" Reflist ")" ]
Comment = "#" *VCHAR
YYYYMMDD is an integer, in alphabetic form, representing a date, where YYYY is the 4-digit year, MM is the 2-digit month, and DD is the 2-digit day.
YYYYMMDD是一個整數(shù)，以字母形式表示日期，其中YYYY是4位數(shù)字的年份，MM是2位數(shù)字的月份，DD是2位數(shù)字的日期。
5.2. Comments and Explanation of Syntax
5.2. 語法注釋與解釋
Any lines starting with, or portions of lines after, the hash symbol("#") are treated as comments. Comments have no significance in the processing of the tables; nor are there any syntax requirements between the hash symbol and the end of the line. Blank lines in the tables are ignored completely.
以散列符號（“#”）開頭的任何行或其后的部分行都被視為注釋。注釋在表格處理中沒有意義；哈希符號和行尾之間也沒有任何語法要求。表格中的空行將被完全忽略。
Every language should have its own Language Variant Table provided by a relevant group, organization, or other body. That table will normally be based on some established standard or standards. The group that defines a Language Variant Table should document references to the appropriate standards at the beginning of the table, tagged with the word "Reference" followed by an integer (the reference number) followed by the description of the reference. For example:
每種語言都應(yīng)該有自己的語言變體表，由相關(guān)團體、組織或其他機構(gòu)提供。該表通常基于一些既定標準。定義語言變量表的小組應(yīng)在表的開頭記錄對適當標準的引用，標記為“引用”一詞，后跟整數(shù)（引用號），后跟引用說明。例如：
Reference 1 CP936 (commonly known as GBK) Reference 2 zVariant, zTradVariant, zSimpVariant in Unihan.txt Reference 3 List of Simplified Character Table (Simplified column) Reference 4 zSimpVariant in Unihan.txt Reference 5 Variant that exists in GB2312, common simplified Hanzi
參考文獻1 CP936（俗稱GBK）參考文獻2 Unihan.txt中的zVariant、zTradVariant、zSimpVariant參考文獻3簡化字符表列表（簡化列）參考文獻4 Unihan.txt中的zSimpVariant參考文獻5 GB2312中存在的變體，通用簡化漢字
Each Language Variant Table must have a version number and its release date. This is tagged with the word "Version" followed by an integer then followed by the date in the format YYYYMMDD, where YYYY is the 4-digit year, MM is the 2-digit month, and DD is the 2-digit day of the publication date of the table.
每個語言變體表必須有版本號及其發(fā)布日期。該表標記為“版本”，后跟一個整數(shù)，然后是格式為YYYYMMDD的日期，其中YYYY是4位數(shù)的年份，MM是2位數(shù)的月份，DD是表的發(fā)布日期的2位數(shù)的日期。
Version 1 20020701 # July 2002 Version 1
版本1 20020701#2002年7月版本1
The table has three columns, separated by semicolons: "Valid Code Point"; "Preferred Variant(s)"; and "Character Variant(s)".
該表有三列，以分號分隔：“有效代碼點”；“首選變體”；及"字符變體。
The "Valid Code Point" is the subset of Unicode characters that are valid to be registered.
“有效代碼點”是可有效注冊的Unicode字符的子集。
There can be more than one Preferred Variant; hence there could be multiple entries in the "Preferred Variant(s)" column. If the "Preferred Variant(s)" column is empty, then there is no corresponding Preferred Variant; in other words, the Preferred Variant is null, there is no corresponding preferred variant codepoint, and no processing to add labels for preferred variants occurs." Unless local policy dictates otherwise, the procedures above will result in only those labels that reflect the valid code point being activated (registered) into the zone file.
可以有多個首選變體；因此，“首選變量”列中可能有多個條目。如果“首選變量”列為空，則沒有相應(yīng)的首選變量；換句話說，首選變量為空，沒有相應(yīng)的首選變量代碼點，并且沒有為首選變量添加標簽的處理?！背钱?shù)卣吡碛幸?guī)定，否則上述過程將導致僅將反映有效代碼點的標簽激活（注冊）到區(qū)域文件中。
The "Character Variant(s)" column contains all Character Variants of the Code Point. Since the Code Point is always a variant of itself, to avoid redundancy, the Code Point is assumed to be part of the "Character Variant(s)" and need not be repeated in the "Character Variant(s)" column.
“字符變體”列包含代碼點的所有字符變體。由于代碼點始終是其自身的變體，為避免冗余，代碼點被假定為“字符變體”的一部分，無需在“字符變體”列中重復。
If the variant in the "Preferred Variant(s)" or the "Character Variant(s)" column is composed of a sequence of Code Points, then sequence of Code Points is listed separated by a space.
如果“首選變量”或“字符變量”列中的變量由一系列代碼點組成，則代碼點序列以空格分隔。
If there are multiple variants in the "Preferred Variant(s)" or the "Character Variant(s)" column, then each variant is separated by a comma.
如果“首選變量”或“字符變量”列中有多個變量，則每個變量用逗號分隔。
Any Code Point listed in the "Preferred Variant(s)" column must be allowed by the rules for the relevant language to be registered. However, this is not a requirement for the entries in the "Character Variant(s)" column; it is possible that some of those entries may not be allowed to be registered.
“首選變體”列中列出的任何代碼點必須得到相關(guān)語言注冊規(guī)則的允許。但是，“字符變體”列中的條目不要求這樣做；其中一些條目可能不允許注冊。
Every Code Point in the table should have a corresponding reference number (associated with the references) specified to justify the entry. The reference number is placed in parentheses after the Code Point. If there is more than one reference, then the numbers are placed within a single set of parentheses and separated by commas.
表中的每個代碼點都應(yīng)指定相應(yīng)的參考編號（與參考關(guān)聯(lián)），以證明條目的合理性。參考號放在代碼點后的括號中。如果有多個引用，則將數(shù)字放在一組括號內(nèi)，并用逗號分隔。
6. Security Considerations
6. 安全考慮
As discussed in the Introduction, substantially-unrestricted use of international (non-ASCII) characters in domain name labels may cause user confusion and invite various types of attacks. In particular, in the case of CJK languages, an attacker has an opportunity to divert or confuse users as a result of different characters (or, more specifically, assigned code points) with identical or similar semantics. These Guidelines provide a partial remedy for those risks by supplying a framework for prohibiting inappropriate characters from being registered at all and for permitting "variant" characters to be grouped together and reserved, so that they can only be registered in the DNS by the same owner. However, the system it suggests is no better or worse than the per-zone and per-language tables whose format and use this document specifies. Specific tables, and any additional local processing, will reflect per-zone decisions about the balance between risk and flexibility of registrations. And, of course, errors in construction of those tables may significantly reduce the quality of protection provided.
正如引言中所討論的，在域名標簽中基本上不受限制地使用國際（非ASCII）字符可能會導致用戶混淆，并引發(fā)各種類型的攻擊。特別是在CJK語言的情況下，由于具有相同或類似語義的不同字符（或更具體地說，指定的代碼點），攻擊者有機會轉(zhuǎn)移或混淆用戶。這些指南提供了一個框架，用于禁止不適當?shù)淖址?，并允許將“變體”字符分組并保留，以便它們只能由同一所有者在DNS中注冊，從而為這些風險提供了部分補救措施。然而，它所建議的系統(tǒng)并不比本文檔指定的格式和用途的每區(qū)域和每語言表更好或更差。具體表格和任何額外的本地處理將反映每個區(qū)域關(guān)于注冊風險和靈活性之間平衡的決定。當然，這些表的構(gòu)造錯誤可能會顯著降低所提供保護的質(zhì)量。
7. Index to Terminology
7. 術(shù)語索引
As a convenience to the reader, this section lists all of the special terminology used in this document, with a pointer to the section in which it is defined.
為方便讀者閱讀，本節(jié)列出了本文件中使用的所有特殊術(shù)語，并附有一個指向定義該術(shù)語的章節(jié)的指針。
Activated Label 2.1.17 Activation 2.1.4 Active Label 2.1.17 Character Variant 2.1.14 Character Variant Label 2.1.16 CJK Characters 2.1.9
激活標簽2.1.17激活2.1.4激活標簽2.1.17字符變體2.1.14字符變體標簽2.1.16 CJK字符2.1.9
Code point 2.1.7 Code Point Variant 2.1.14 FQDN 2.1.3 Hostname 2.1.1 IDL 2.1.2 IDL Package 2.1.18 IDN 2.1.1 Internationalized Domain Label 2.1.2 ISO/IEC 10646 2.1.6 Label String 2.1.10 Language name codes 2.1.5 Language Variant Table 2.1.11 LDH Subset 2.1.1 Preferred Code Point 2.1.13 Preferred Variant 2.1.13 Preferred Variant Label 2.1.15 Registration 2.1.4 Reserved 2.1.18 RFC3066 2.1.5 Table 2.1.11 UCS 2.1.6 Unicode Character 2.1.7 Unicode String 2.1.8 Valid Code Point 2.1.12 Variant Table 2.1.11 Zone Variant 2.1.17
Code point 2.1.7 Code Point Variant 2.1.14 FQDN 2.1.3 Hostname 2.1.1 IDL 2.1.2 IDL Package 2.1.18 IDN 2.1.1 Internationalized Domain Label 2.1.2 ISO/IEC 10646 2.1.6 Label String 2.1.10 Language name codes 2.1.5 Language Variant Table 2.1.11 LDH Subset 2.1.1 Preferred Code Point 2.1.13 Preferred Variant 2.1.13 Preferred Variant Label 2.1.15 Registration 2.1.4 Reserved 2.1.18 RFC3066 2.1.5 Table 2.1.11 UCS 2.1.6 Unicode Character 2.1.7 Unicode String 2.1.8 Valid Code Point 2.1.12 Variant Table 2.1.11 Zone Variant 2.1.17translate error, please retry
8. Acknowledgments
8. 致謝
The authors gratefully acknowledge the contributions of:
作者衷心感謝以下方面的貢獻：
- V. CHEN, N. HSU, H. HOTTA, S. TASHIRO, Y. YONEYA, and other Joint Engineering Team members at the JET meeting in Bangkok, Thailand.
- V.CHEN、N.HSU、H.HOTTA、S.TASHIRO、Y.YONEYA和其他聯(lián)合工程團隊成員出席了在泰國曼谷舉行的JET會議。
- Yves Arrouye, an observer at the JET meeting in Bangkok, for his contribution on the IDL Package.
- 伊夫·阿羅耶（Yves Arrouye），曼谷噴氣式飛機會議觀察員，感謝他對IDL計劃的貢獻。
- Those who commented on, and made suggestions about, earlier versions, including Harald ALVESTRAND, Erin CHEN, Patrik FALTSTROM, Paul HOFFMAN, Soobok LEE, LEE Xiaodong, MAO Wei, Erik NORDMARK, and L.M. TSENG.
- 那些對早期版本發(fā)表評論并提出建議的人，包括哈拉爾·阿爾維斯特朗、陳艾琳、帕特里克·法茨特羅姆、保羅·霍夫曼、李秀博、李曉東、毛偉、埃里克·諾德馬克和曾立明。
9. References
9. 工具書類
9.1. Normative References
9.1. 規(guī)范性引用文件
[ABNF] Crocker, D. and P. Overell, Eds., "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.
[ABNF]Crocker，D.和P.Overell，編輯，“語法規(guī)范的擴充BNF:ABNF”，RFC 2234，1997年11月。
[STD13] Mockapetris, P., "Domain names concepts and facilities" STD 13, RFC 1034, November 1987. Mockapetris, P., "Domain names implementation and specification", STD 13, RFC 1035, November 1987.
[STD13]Mockapetris，P.，“域名概念和設(shè)施”STD 13，RFC 1034，1987年11月。Mockapetris，P.，“域名實現(xiàn)和規(guī)范”，STD 13，RFC 10351987年11月。
[RFC3066] Alvestrand, H., "Tags for the Identification of Languages," BCP 47, RFC 3066, January 2001.
[RFC3066]Alvestrand，H.，“語言識別標簽”，BCP 47，RFC 3066，2001年1月。
[IDNA] Faltstrom, P., Hoffman, P. and A. M. Costello, "Internationalizing Domain Names in Applications (IDNA)", RFC 3490, March 2003.
[IDNA]Faltstrom，P.，Hoffman，P.和A.M.Costello，“應(yīng)用程序中的域名國際化（IDNA）”，RFC 34902003年3月。
[PUNYCODE] Costello, A.M., "Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA)", RFC 3492, March 2003.
[PUNYCODE]Costello，A.M.，“PUNYCODE：應(yīng)用程序中國際化域名的Unicode引導字符串編碼（IDNA）”，RFC 3492，2003年3月。
[STRINGPREP] Hoffman, P. and M. Blanchet, "Preparation of Internationalized Strings ("stringprep")", RFC 3454, December 2002.
[STRINGPREP]Hoffman，P.和M.Blanchet，“國際化弦的準備（“STRINGPREP”）”，RFC 3454，2002年12月。
[NAMEPREP] Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)", RFC 3491, March 2003.
[NAMEPREP]Hoffman，P.和M.Blanchet，“NAMEPREP：國際化域名（IDN）的Stringprep配置文件”，RFC 34912003年3月。
[IS10646] A product of ISO/IEC JTC1/SC2/WG2, Work Item JTC1.02.18 (ISO/IEC 10646). It is a multipart standard: Part 1, published as ISO/IEC 10646- 1:2000(E), covers the Architecture and Basic Multilingual Plane, and Part 2, published as ISO/IEC 10646-2:2001(E), covers the supplementary (additional) planes.
[IS10646]是ISO/IEC JTC1/SC2/WG2工作項JTC1.02.18（ISO/IEC 10646）的產(chǎn)品。它是一個多部分標準：第1部分（以ISO/IEC 10646-1:2000（E）的形式發(fā)布）涵蓋了體系結(jié)構(gòu)和基本多語言平面，第2部分（以ISO/IEC 10646-2:2001（E）的形式發(fā)布）涵蓋了補充（附加）平面。
[UNIHAN] Unicode Han Database, Unicode Consortium ftp://ftp.unicode.org/Public/UNIDATA/Unihan.txt.
[UNIHAN]Unicode Han數(shù)據(jù)庫，Unicode聯(lián)盟ftp://ftp.unicode.org/Public/UNIDATA/Unihan.txt.
[UNICODE] The Unicode Consortium, "The Unicode Standard Version 3.0," ISBN 0-201-61633-5. Unicode Standard Annex #28 (http://www.unicode.org/unicode/reports/tr28/) defines Version 3.2 of the Unicode Standard, which is definitive for IDNA and this document.
[UNICODE]UNICODE聯(lián)盟，“UNICODE標準版本3.0”，ISBN 0-201-61633-5。Unicode標準附件#28(http://www.unicode.org/unicode/reports/tr28/)定義Unicode標準的3.2版，這是IDNA和本文檔的最終版本。
[ISO7098] ISO 7098;1991 Information and documentation Romanization of Chinese, ISO/TC46/SC2.
[ISO7098]ISO7098；1991信息和文件中文羅馬化，ISO/TC46/SC2。
9.2. Informative References
9.2. 資料性引用
[IANA-LVTABLES] Internet Assigned Numbers Authority (IANA), IDN
Character Registry.
http://www.iana.org/assignments/idn/
[IANA-LVTABLES] Internet Assigned Numbers Authority (IANA), IDN
Character Registry.
http://www.iana.org/assignments/idn/
[IDN-WG] IETF Internationalized Domain Names Working Group, now concluded,idn@ops.ietf.org, James Seng, Marc Blanchet, co-chairs, http://www.i-d-n.net/.
[IDN-WG]IETF國際化域名工作組，現(xiàn)已結(jié)束，idn@ops.ietf.org，James Seng，Marc Blanchet，聯(lián)合主席，http://www.i-d-n.net/.
[UDRP] ICANN, "Uniform Domain Name Dispute Resolution
Policy", October 1999,
http://www.icann.org/udrp/udrp-policy-24oct99.htm
[UDRP] ICANN, "Uniform Domain Name Dispute Resolution
Policy", October 1999,
http://www.icann.org/udrp/udrp-policy-24oct99.htm
[ISO639] "ISO 639:1988 (E/F) Code for the representation of names of languages", International Organization for Standardization, 1st edition, 1988-04-01.
[ISO639]“ISO 639:1988（E/F）語言名稱表示代碼”，國際標準化組織，第1版，1988-04-01。
10. Contributors
10. 貢獻者
The formal responsibility for this document and the ideas it contains lie with K. Koniski, K. Huang, H. Qian, and Y. Ko. These authors are listed on the first page as authors of record, and they are the appropriate the long-term contacts for questions and comments on this RFC. On the other hand, J. Seng, J. Klensin, and W. Rickard served as editors of the document, transcribing and translating the ideas of the four authors and the teams they represented into the current written form. They were the primary contacts during the editing process, but not in the long term.
本文件及其包含的思想由K.Koniski、K.Huang、H.Qian和Y.Ko承擔正式責任。這些作者作為記錄作者列在第一頁上，他們是本RFC問題和評論的長期聯(lián)系人。另一方面，J.Seng、J.Klensin和W.Rickard擔任該文件的編輯，將四位作者及其代表的團隊的想法轉(zhuǎn)錄并翻譯成當前的書面形式。他們是編輯過程中的主要聯(lián)系人，但不是長期聯(lián)系人。
10.1. Authors' Addresses
10.1. 作者地址
Kazunori KONISHI JPNIC Kokusai-Kougyou-Kanda Bldg 6F 2-3-4 Uchi-Kanda, Chiyoda-ku Tokyo 101-0047 Japan
日本東京千代田區(qū)內(nèi)神田2-3-4樓Kokusai Kougyou Kanda大廈6樓
Phone: +81 49-278-7313
EMail: konishi@jp.apan.net
Phone: +81 49-278-7313
EMail: konishi@jp.apan.net
Kenny HUANG TWNIC 3F, 16, Kang Hwa Street, Taipei Taiwan
臺灣臺北市康華街16號黃建豪三樓
Phone: 886-2-2658-6510 EMail: huangk@alum.sinica.edu
電話：886-2-2658-6510電子郵件：huangk@alum.sinica.edu
QIAN Hualin CNNIC No.6 Branch-box of No.349 Mailbox, Beijing 100080 Peoples Republic of China
錢華林中國互聯(lián)網(wǎng)絡(luò)信息中心349號郵箱6號分機箱，中華人民共和國北京100080
EMail: Hlqian@cnnic.net.cn
EMail: Hlqian@cnnic.net.cn
KO YangWoo PeaceNet Yangchun P.O. Box 81 Seoul 158-600 Korea
高陽宇和平網(wǎng)陽春郵政信箱81首爾158-600韓國
EMail: yw@mrko.pe.kr
EMail: yw@mrko.pe.kr
10.2. Editors' Addresses
10.2. 編輯地址
James SENG 180 Lompang Road #22-07 Singapore 670180 Phone: +65 9638-7085
James SENG Lompang路180號#22-07新加坡670180電話：+65 9638-7085
EMail: jseng@pobox.org.sg
EMail: jseng@pobox.org.sg
John C KLENSIN 1770 Massachusetts Avenue, No. 322 Cambridge, MA 02140 U.S.A.
美國馬薩諸塞州劍橋322號馬薩諸塞大道1770號，郵編02140。
EMail: Klensin+ietf@jck.com
EMail: Klensin+ietf@jck.com
Wendy RICKARD The Rickard Group 16 Seminary Ave Hopewell, NJ 08525 USA
溫迪·里卡德美國新澤西州霍普韋爾神學院16號里卡德集團，郵編：08525
EMail: rickard@rickardgroup.com
EMail: rickard@rickardgroup.com
11. Full Copyright Statement
11. 完整版權(quán)聲明
Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78 and except as set forth therein, the authors retain all their rights.
版權(quán)所有（C）互聯(lián)網(wǎng)協(xié)會（2004年）。本文件受BCP 78中包含的權(quán)利、許可和限制的約束，除其中規(guī)定外，作者保留其所有權(quán)利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原樣”提供的，貢獻者、他/她所代表或贊助的組織（如有）、互聯(lián)網(wǎng)協(xié)會和互聯(lián)網(wǎng)工程任務(wù)組不承擔任何明示或暗示的擔保，包括但不限于任何保證，即使用本文中的信息不會侵犯任何權(quán)利，或?qū)m銷性或特定用途適用性的任何默示保證。
Intellectual Property
知識產(chǎn)權(quán)
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF對可能聲稱與本文件所述技術(shù)的實施或使用有關(guān)的任何知識產(chǎn)權(quán)或其他權(quán)利的有效性或范圍，或此類權(quán)利下的任何許可可能或可能不可用的程度，不采取任何立場；它也不表示它已作出任何獨立努力來確定任何此類權(quán)利。有關(guān)RFC文件中權(quán)利的程序信息，請參見BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘書處披露的知識產(chǎn)權(quán)副本和任何許可證保證，或本規(guī)范實施者或用戶試圖獲得使用此類專有權(quán)利的一般許可證或許可的結(jié)果，可從IETF在線知識產(chǎn)權(quán)存儲庫獲取，網(wǎng)址為http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀請任何相關(guān)方提請其注意任何版權(quán)、專利或?qū)＠暾?，或其他可能涵蓋實施本標準所需技術(shù)的專有權(quán)利。請將信息發(fā)送至IETF的IETF-ipr@ietf.org.
Acknowledgement
確認
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC編輯功能的資金目前由互聯(lián)網(wǎng)協(xié)會提供。
