Reverse DNS in IPv6 for Internet Service Providers
draft-howard-isp-ip6rdns-08
| Document | Type |
Replaced Internet-Draft
(candidate for dnsop WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Lee Howard | ||
| Last updated | 2015-10-14 (Latest revision 2015-05-14) | ||
| Replaced by | draft-ietf-dnsop-isp-ip6rdns, RFC 8501 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-dnsop-isp-ip6rdns, draft-ietf-dnsop-isp-ip6rdns | |
| Consensus boilerplate | Unknown | ||
| 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 and considerations for ISPs in managing 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.)