Reverse DNS in IPv6 for Internet Service Providers
draft-ietf-dnsop-isp-ip6rdns-03
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Expired Internet-Draft (dnsop WG) | |
| Last updated | 2017-09-16 (latest revision 2017-03-15) | ||
| Replaces | draft-howard-isp-ip6rdns | ||
| Stream | IETF | ||
| Intended RFC status | Informational | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Reviews | |||
| Stream | WG state | In WG Last Call | |
| Document shepherd | Suzanne Woolf | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | "Tim Wicinski" <tjw.ietf@gmail.com>, "Suzanne Woolf" <suzworldwide@gmail.com> | ||
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-ietf-dnsop-isp-ip6rdns-03.txt
https://www.ietf.org/archive/id/draft-ietf-dnsop-isp-ip6rdns-03.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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)