Reverse Name Lookups of Encapsulated IPv4 Addresses in IPv6
draft-vixie-ipng-ipv4ptr-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Paul A. Vixie | ||
| Last updated | 1996-05-23 | ||
| 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
[RFC1884] specified two IPv6 address forms that encapsulated IPv4 addresses. [RFC1886] specified a new DNS RR type (AAAA) to map domain names to IPv6 addresses, and also specified the form of the PTR RR owner name used to map IPv6 addresses back to the domain name of that host or interface. This memo amends [RFC1886] and gives two exceptions to its rules regarding PTR RR owner name correspondance to IPv6 addresses. Specifically, the two IPv4 encapsulation methods are exempted from [RFC1886]'s nybble mapping, and are made subject to the appropriate rules from [RFC1035] and [RFC1101].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)