Reverse DNS in IPv6 for Internet Service Providers
RFC 8501

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: tjw.ietf@gmail.com, The IESG <iesg@ietf.org>, draft-ietf-dnsop-isp-ip6rdns@ietf.org, dnsop-chairs@ietf.org, Benno Overeinder <benno@NLnetLabs.nl>, dnsop@ietf.org, Tim Wicinski <tjw.ietf@gmail.com>, Suzanne Woolf <suzworldwide@gmail.com>, warren@kumari.net, rfc-editor@rfc-editor.org
Subject: Document Action: 'Reverse DNS in IPv6 for Internet Service Providers' to Informational RFC (draft-ietf-dnsop-isp-ip6rdns-07.txt)

The IESG has approved the following document:
- 'Reverse DNS in IPv6 for Internet Service Providers'
  (draft-ietf-dnsop-isp-ip6rdns-07.txt) as Informational RFC

This document is the product of the Domain Name System Operations Working
Group.

The IESG contact persons are Warren Kumari and Ignas Bagdonas.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-isp-ip6rdns/


Technical Summary

    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.

Working Group Summary

   This document was reviewed pretty extensively.  There were several 
issues brought up during the document, which the authors and the
working group were able to resolve over time.  Since the 
document presents operational guidance, there is no specific 
implementations needed. 

Document Quality

   Operational advice / discussions - no implementation needed.
   Document is an easy read, clear and concise.  

Personnel

   Document Shepherd: Tim Wicinski   
   Area Director:    Warren Kumari