<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.hoffman-rfc3490bis" target="https://datatracker.ietf.org/doc/html/draft-hoffman-rfc3490bis-02">
   <front>
      <title>Internationalizing Domain Names in Applications (IDNA)</title>
      <author initials="P." surname="Fältström" fullname="Patrik Fältström">
         <organization>Cisco</organization>
      </author>
      <author initials="P. E." surname="Hoffman" fullname="Paul E. Hoffman">
         <organization>IMC &amp; VPNC</organization>
      </author>
      <author initials="A. M." surname="Costello" fullname="Adam M. Costello">
         <organization>UC Berkeley</organization>
      </author>
      <date month="April" day="14" year="2004" />
      <abstract>
	 <t>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.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-hoffman-rfc3490bis-02" />
   
</reference>
