Reverse DNS in IPv6 for Internet Service Providers
draft-howard-isp-ip6rdns-08
| Document | Type | Replaced Internet-Draft (candidate for dnsop WG) | |
|---|---|---|---|
| Last updated | 2015-10-14 (latest revision 2015-05-14) | ||
| Replaced by | draft-ietf-dnsop-isp-ip6rdns | ||
| Stream | IETF | ||
| Intended RFC status | Informational | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-dnsop-isp-ip6rdns | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-howard-isp-ip6rdns-08.txt
https://www.ietf.org/archive/id/draft-howard-isp-ip6rdns-08.txt
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
Lee Howard (lee.howard@twcable.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)