draft-ietf-dnsop-isp-ip6rdns-04.txt   draft-ietf-dnsop-isp-ip6rdns-05.txt 
Network Working Group L. Howard Network Working Group L. Howard
Internet-Draft Retevia Internet-Draft Retevia
Intended status: Informational November 15, 2017 Intended status: Informational April 25, 2018
Expires: May 19, 2018 Expires: October 27, 2018
Reverse DNS in IPv6 for Internet Service Providers Reverse DNS in IPv6 for Internet Service Providers
draft-ietf-dnsop-isp-ip6rdns-04 draft-ietf-dnsop-isp-ip6rdns-05
Abstract Abstract
In IPv4, Internet Service Providers (ISPs) commonly provide IN- In IPv4, Internet Service Providers (ISPs) commonly provide IN-
ADDR.ARPA information for their customers by prepopulating the zone ADDR.ARPA information for their customers by prepopulating the zone
with one PTR record for every available address. This practice does with one PTR record for every available address. This practice does
not scale in IPv6. This document analyzes different approaches and not scale in IPv6. This document analyzes different approaches and
considerations for ISPs in managing the ip6.arpa zone for IPv6 considerations for ISPs in managing the ip6.arpa zone for IPv6
address space assigned to many customers. address space assigned to many customers.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 19, 2018. This Internet-Draft will expire on October 27, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 41 skipping to change at page 3, line 41
254.2.0.192.IN-ADDR.ARPA. IN PTR 254.string.region.example.com. 254.2.0.192.IN-ADDR.ARPA. IN PTR 254.string.region.example.com.
The conscientious Example.com might then also have a zone: The conscientious Example.com might then also have a zone:
1.string.region.example.com. IN A 192.0.2.1 1.string.region.example.com. IN A 192.0.2.1
2.string.region.example.com. IN A 192.0.2.2 2.string.region.example.com. IN A 192.0.2.2
3.string.region.example.com. IN A 192.0.2.3 3.string.region.example.com. IN A 192.0.2.3
\. .
\. .
\. .
254.string.region.example.com. IN A 192.0.2.254 254.string.region.example.com. IN A 192.0.2.254
Many ISPs generate PTR records for all IP addresses used for Many ISPs generate PTR records for all IP addresses used for
customers, and many create the matching A record. customers, and many create the matching A record.
1.2. Reverse DNS Considerations in IPv6 1.2. Reverse DNS Considerations in IPv6
A sample entry for 2001:0db8:0f00:0000:0012:34ff:fe56:789a might be: A sample entry for 2001:0db8:0f00:0000:0012:34ff:fe56:789a might be:
skipping to change at page 12, line 18 skipping to change at page 12, line 18
information about a user compromises that user's privacy. Some users information about a user compromises that user's privacy. Some users
may want to identify their hosts using user-specified hostnames, but may want to identify their hosts using user-specified hostnames, but
the default behavior should not be to identify a user, their the default behavior should not be to identify a user, their
location, their connectivity, or other information in a PTR record. location, their connectivity, or other information in a PTR record.
7. Acknowledgements 7. Acknowledgements
The author would like to thank Alain Durand, JINMEI Tatuya, David The author would like to thank Alain Durand, JINMEI Tatuya, David
Freedman, Andrew Sullivan, Chris Griffiths, Darryl Tanner, Ed Lewis, Freedman, Andrew Sullivan, Chris Griffiths, Darryl Tanner, Ed Lewis,
John Brzozowski, Chris Donley, Wes George, Jason Weil, John Spence, John Brzozowski, Chris Donley, Wes George, Jason Weil, John Spence,
Ted Lemon, Stephan Lagerholm, Steinar Haug, Mark Andrews, and Chris Ted Lemon, Stephan Lagerholm, Steinar Haug, Mark Andrews, Chris
Roosenraad, Fernando Gont, John Levine, and many others who discussed Roosenraad, Fernando Gont, John Levine, and many others who discussed
and provided suggestions for this document. and provided suggestions for this document.
8. IANA Considerations 8. IANA Considerations
There are no IANA considerations or implications that arise from this There are no IANA considerations or implications that arise from this
document. document.
9. References 9. References
skipping to change at page 14, line 9 skipping to change at page 14, line 9
[hostname] Huitema, C., Thaler, D., and R. Winter, "draft-ietf- [hostname] Huitema, C., Thaler, D., and R. Winter, "draft-ietf-
intarea-hostname-practice", February 2017. intarea-hostname-practice", February 2017.
Author's Address Author's Address
Lee Howard Lee Howard
Retevia Retevia
Fairfax, VA 22032 Fairfax, VA 22032
USA USA
Email: lee@asgard.org Email: lee.howard@retevia.net
 End of changes. 9 change blocks. 
9 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/