xNAME loop detection and its usage suggestion
draft-yao-dnsop-xname-loop-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jiankang Yao , XiaoDong Lee | ||
| Last updated | 2012-05-17 (Latest revision 2011-11-14) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Domain Name System (DNS) has provided some means, such as CNAME or DNAME, where a query can be redirected to a different name. The zone operator should be careful about this redirection, which may forms a loop. The detail analysis of xNAME loop detection and its impacts are not specified in the RFC 1035 and RFC 2672. This document gives a detail analysis of xNAME loop and its impacts. It also gives some advices for using xNAME.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)