| < draft-ietf-dnsop-root-loopback-02.txt | draft-ietf-dnsop-root-loopback-03.txt > | |||
|---|---|---|---|---|
| Network Working Group W. Kumari | Network Working Group W. Kumari | |||
| Internet-Draft Google | Internet-Draft Google | |||
| Intended status: Informational P. Hoffman | Intended status: Informational P. Hoffman | |||
| Expires: December 27, 2015 VPN Consortium | Expires: February 12, 2016 ICANN | |||
| June 25, 2015 | August 11, 2015 | |||
| Decreasing Access Time to Root Servers by Running One on Loopback | Decreasing Access Time to Root Servers by Running One on Loopback | |||
| draft-ietf-dnsop-root-loopback-02 | draft-ietf-dnsop-root-loopback-03 | |||
| Abstract | Abstract | |||
| Some DNS recursive resolvers have longer-than-desired round trip | Some DNS recursive resolvers have longer-than-desired round trip | |||
| times to the closest DNS root server. Some DNS recursive resolver | times to the closest DNS root server. Some DNS recursive resolver | |||
| operators want to prevent snooping of requests sent to DNS root | operators want to prevent snooping of requests sent to DNS root | |||
| servers by third parties. Such resolvers can greatly decrease the | servers by third parties. Such resolvers can greatly decrease the | |||
| round trip time and prevent observation of requests by running a copy | round trip time and prevent observation of requests by running a copy | |||
| of the full root zone on a loopback address (such as 127.0.0.1). | of the full root zone on a loopback address (such as 127.0.0.1). | |||
| This document shows how to start and maintain such a copy of the root | This document shows how to start and maintain such a copy of the root | |||
| skipping to change at page 1, line 39 ¶ | skipping to change at page 1, line 39 ¶ | |||
| 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 http://datatracker.ietf.org/drafts/current/. | Drafts is at http://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 December 27, 2015. | This Internet-Draft will expire on February 12, 2016. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2015 IETF Trust and the persons identified as the | Copyright (c) 2015 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 | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://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 | |||
| skipping to change at page 6, line 34 ¶ | skipping to change at page 6, line 34 ¶ | |||
| Doug Barton, Greg Lindsay, and Akira Kato. The authors also received | Doug Barton, Greg Lindsay, and Akira Kato. The authors also received | |||
| many off-line comments about making the document clear that this was | many off-line comments about making the document clear that this was | |||
| just a description of a way to operate a root zone on localhost, and | just a description of a way to operate a root zone on localhost, and | |||
| not a recommendation to do so. | not a recommendation to do so. | |||
| 8. References | 8. References | |||
| 8.1. Normative References | 8.1. Normative References | |||
| [RFC1035] Mockapetris, P., "Domain names - implementation and | [RFC1035] Mockapetris, P., "Domain names - implementation and | |||
| specification", STD 13, RFC 1035, November 1987. | specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, | |||
| November 1987, <http://www.rfc-editor.org/info/rfc1035>. | ||||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, March 1997. | Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ | |||
| RFC2119, March 1997, | ||||
| <http://www.rfc-editor.org/info/rfc2119>. | ||||
| 8.2. Informative References | 8.2. Informative References | |||
| [AggressiveNSEC] | [AggressiveNSEC] | |||
| Fujiwara, K. and A. Kato, "Aggressive use of NSEC/NSEC3", | Fujiwara, K. and A. Kato, "Aggressive use of NSEC/NSEC3", | |||
| draft-fujiwara-dnsop-nsec-aggressiveuse-00 (work in | draft-fujiwara-dnsop-nsec-aggressiveuse-00 (work in | |||
| progress), 2015. | progress), 2015. | |||
| [Manning2013] | [Manning2013] | |||
| Maning, W., "Client Based Naming", 2013, | Maning, W., "Client Based Naming", 2013, | |||
| <http://www.sfc.wide.ad.jp/dissertation/bill_e.html>. | <http://www.sfc.wide.ad.jp/dissertation/bill_e.html>. | |||
| Appendix A. Current Sources of the Root Zone | Appendix A. Current Sources of the Root Zone | |||
| The root zone can be retrieved from anywhere as long as it comes with | The root zone can be retrieved from anywhere as long as it comes with | |||
| all the DNSSEC records needed for validation. Currently, there are | all the DNSSEC records needed for validation. Currently, one can get | |||
| three sources of the root zone supported by ICANN: | the root zone from ICANN by zone transfer (AXFR) over TCP from DNS | |||
| servers at xfr.lax.dns.icann.org and xfr.cjr.dns.icann.org. | ||||
| o From ICANN via FTP at ftp://rs.internic.net/domain/root.zone | ||||
| o From ICANN via HTTP at http://www.internic.net/domain/root.zone | ||||
| o From ICANN by zone transfer (AXFR) over TCP from DNS servers at | ||||
| xfr.lax.dns.icann.org and xfr.cjr.dns.icann.org | ||||
| Currently, the root can also be retrieved by AXFR over TCP from the | Currently, the root can also be retrieved by AXFR over TCP from the | |||
| following root server operators: | following root server operators: | |||
| o b.root-servers.net | o b.root-servers.net | |||
| o c.root-servers.net | o c.root-servers.net | |||
| o f.root-servers.net | o f.root-servers.net | |||
| skipping to change at page 11, line 30 ¶ | skipping to change at page 11, line 30 ¶ | |||
| DNSSEC validation for remote responses" is selected. | DNSSEC validation for remote responses" is selected. | |||
| Authors' Addresses | Authors' Addresses | |||
| Warren Kumari | Warren Kumari | |||
| Email: Warren@kumari.net | Email: Warren@kumari.net | |||
| Paul Hoffman | Paul Hoffman | |||
| VPN Consortium | ICANN | |||
| Email: paul.hoffman@vpnc.org | Email: paul.hoffman@icann.org | |||
| End of changes. 8 change blocks. | ||||
| 16 lines changed or deleted | 13 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||