Internationalizing Domain Names in Applications (IDNA)
draft-hoffman-rfc3490bis-02

Document Type Expired Internet-Draft (individual in int area)
Last updated 2015-10-14 (latest revision 2004-04-14)
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state Expired (IESG: Dead)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Scott Hollenbeck
Send notices to amc+q3tovu@nicemice.net, Marc.Blanchet@hexago.com

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-hoffman-rfc3490bis-02.txt

Abstract

Until now, there has been no standard method for domain names to use characters outside the ASCII repertoire. This document defines internationalized domain names (IDNs) and a mechanism called Internationalizing Domain Names in Applications (IDNA) for handling them in a standard fashion. IDNs use characters drawn from a large repertoire (Unicode), but IDNA allows the non-ASCII characters to be represented using only the ASCII characters already allowed in so- called host names today. This backward-compatible representation is required in existing protocols like DNS, so that IDNs can be introduced with no changes to the existing infrastructure. IDNA is only meant for processing domain names, not free text.

Authors

Patrik Fältström (paf@cisco.com)
Paul Hoffman (paul.hoffman@vpnc.org)
Adam Costello (amc@cs.berkley.edu)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)