Mapping Characters in IDNA
draft-ietf-idnabis-mappings-05
| Document | Type | Expired Internet-Draft (idnabis WG) | |
|---|---|---|---|
| Authors | Pete Resnick , Paul E. Hoffman | ||
| Last updated | 2015-10-14 (Latest revision 2009-10-19) | ||
| Replaced by | RFC 5895 | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Lisa M. Dusseault | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-ietf-idnabis-mappings-05.txt
Abstract
In the original version of the Internationalized Domain Names in Applications (IDNA) protocol, any Unicode code points taken from user input were mapped into a set of Unicode code points that "make sense", which were then encoded and passed to the domain name system (DNS). The current version of IDNA presumes that the input to the protocol comes from a set of "permitted" code points, which it then encodes and passes to the DNS, but does not specify what to do with the result of user input. This document describes the actions that can be taken by an implementation between user input and passing permitted code points to the new IDNA protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)