Document: draft-jabley-reverse-servers-01 Reviewer: Vijay K. Gurbani Review Date: January 18, 2010 IESG Telechat date: January 21, 2010 Summary: This draft is ready for publication as a Proposed Standard. It has 0 major issues, 0 minor issues and 1 nit. Nits: 1) For readability, I would suggest that the text in Section 1 be re-stated as follows: OLD: The Domain Name System (DNS) is described in [RFC1034] and [RFC1035]. The DNS currently supports keyed data retrieval using three namespaces -- domain names, IPv4 addresses and IPv6 addresses. Mapping of IPv4 addresses to names is accomplished using data published in the IN-ADDR.ARPA zone. For IPv6, the IP6.ARPA zone is used (see [RFC3152]). The process of mapping an address to a name is generally known as a "reverse lookup", and the IN-ADDR.ARPA and IP6.ARPA zones are said to support the "reverse DNS". NEW: The Domain Name System (DNS) is described in [RFC1034] and [RFC1035]. The DNS currently supports keyed data retrieval using three namespaces -- domain names, IPv4 addresses and IPv6 addresses. The canonical use of DNS is to resolve domain names to IPv4 or IPv6 addresses, however the reverse is possible as well. The process of mapping an address to a name is generally known as a "reverse lookup"; mapping of IPv4 addresses to names is accomplished using data published in the IN-ADDR.ARPA zone. For IPv6, the IP6.ARPA zone is used (see [RFC3152]). The IN-ADDR.ARPA and IP6.ARPA zones are said to support the "reverse DNS".