IDN TLD Variants Implementation Guideline
draft-yao-dnsop-idntld-implementation-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jiankang Yao , XiaoDong Lee | ||
| Last updated | 2009-10-21 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
ICANN is pushing the IDN TLD into the root server. Some IDN TLD has the variants. Currently, there are two proposals to implement the IDN TLD variants in the root servers:1, implement it with the DNAME record; 2, implement it with NS record. The IDN TLD variants may be reserved or activated. If the IDN TLD variants are activated, these variants will be allocated to the same TLD manager in order to avoid the possible phishing problems. How to deal with the IDN TLD variant issue is a big challenge ahead of us. This document discusses the IDN TLD variants implementation issues related with DNAME and NS resource record way. This memo also gives a proposal about how to avoid the possible phishing problem after putting the IDN TLD variants into the root.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)