Internationalized Domain Names: Alternatives to IDNA
draft-klensin-idna-alternatives-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. John C. Klensin | ||
| Last updated | 2008-02-18 | ||
| 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
The Internet protocol for internationalized domain names (IDNs) is documented in RFC 3490 and associated documents and commonly known as IDNA. While that protocol was being developed (and more recently), there were a number of alternate proposals and suggestions for different ways to do IDNs. IDNA was favored over those alternatives, but variations on them seem to keep reappearing with the suggestion that they are novel ideas. This memo describes some of those suggested alternatives and summarizes the reasons why they were not favored over IDNA.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)