Internationalizing Domain Names for Applications (IDNA): Issues, Explanation, and Rationale
draft-klensin-idnabis-issues-07
| Document | Type |
Expired Internet-Draft
(individual in app area)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. John C. Klensin | ||
| Last updated | 2015-10-14 (Latest revision 2008-02-06) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Chris Newman | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
A recent IAB report identified issues that have been raised with Internationalized Domain Names (IDNs). Some of these issues require tuning of the existing protocols and the tables on which they depend. Based on intensive discussion by an informal design team, this document provides an overview some of the proposals that are being made, provides explanatory material for them and then further explains some of the issues that have been encountered.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)