Problem Statement for Fully Mapping One Name to Another Name
draft-yao-bundled-name-problem-statement-03
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2017-04-30 (latest revision 2016-10-27) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-yao-bundled-name-problem-statement-03.txt
Abstract
This document specifies the problems related to fully mapping one name to another name. With the emergence of internationalized domain names and new TLDs, it is often useful to redirect one domain name tree fully to another domain name tree. Current DNS protocols have not provided such ability to satisfy these requirements.
Authors
Jiankang Yao
(yaojk@cnnic.cn)
XiaoDong Lee
(xl@cnnic.cn)
John Levine
(standards@taugh.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)