Reverse DNS in IPv6 for Internet Service Providers
draft-howard-isp-ip6rdns-04
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Lee Howard , Alain Durand | ||
| Last updated | 2010-09-09 (Latest revision 2010-03-08) | ||
| Replaced by | draft-ietf-dnsop-isp-ip6rdns, RFC 8501 | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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
In IPv4, Internet Service Providers (ISPs) commonly provide IN- ADDR.ARPA. information for their customers by prepopulating the zone with one PTR record for every available address. This practice does not scale in IPv6. This document analyzes different approaches for ISPs to manage the ip6.arpa zone for IPv6 address space assigned to many customers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)