< draft-ietf-dnsop-7706bis-09.txt		draft-ietf-dnsop-7706bis-10.txt >
	Network Working Group W. Kumari		Network Working Group W. Kumari
	Internet-Draft Google		Internet-Draft Google
	Obsoletes: 7706 (if approved) P. Hoffman		Obsoletes: 7706 (if approved) P. Hoffman
	Intended status: Informational ICANN		Intended status: Informational ICANN
	Expires: September 3, 2020 March 2, 2020		Expires: September 6, 2020 March 5, 2020
	Running a Root Server Local to a Resolver		Running a Root Server Local to a Resolver
	draft-ietf-dnsop-7706bis-09		draft-ietf-dnsop-7706bis-10
	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; those resolvers may have		times to the closest DNS root server; those resolvers may have
	difficulty getting responses from the root servers, such as during a		difficulty getting responses from the root servers, such as during a
	network attack. Some DNS recursive resolver operators want to		network attack. Some DNS recursive resolver operators want to
	prevent snooping by third parties of requests sent to DNS root		prevent snooping by third parties of requests sent to DNS root
	servers. Such resolvers can greatly decrease the round-trip time and		servers. Such resolvers can greatly decrease the round-trip time and
	prevent observation of requests by serving a copy of the full root		prevent observation of requests by serving a copy of the full root
	skipping to change at page 1, line 49 ¶		skipping to change at page 1, line 49 ¶
	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 September 3, 2020.		This Internet-Draft will expire on September 6, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 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
	skipping to change at page 8, line 25 ¶		skipping to change at page 8, line 25 ¶
	[RFC8198] Fujiwara, K., Kato, A., and W. Kumari, "Aggressive Use of		[RFC8198] Fujiwara, K., Kato, A., and W. Kumari, "Aggressive Use of
	DNSSEC-Validated Cache", RFC 8198, DOI 10.17487/RFC8198,		DNSSEC-Validated Cache", RFC 8198, DOI 10.17487/RFC8198,
	July 2017, <https://www.rfc-editor.org/info/rfc8198>.		July 2017, <https://www.rfc-editor.org/info/rfc8198>.
	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, one can get		all the DNSSEC records needed for validation. Currently, one can get
	the root zone from ICANN by zone transfer (AXFR) [RFC5936] over TCP		the root zone from ICANN by zone transfer (AXFR) [RFC5936] over TCP
	from DNS servers at xfr.lax.dns.icann.org and xfr.cjr.dns.icann.org.		from DNS servers at xfr.lax.dns.icann.org and xfr.cjr.dns.icann.org.
	One can also get the root zone from IANA as a text file over HTTPS at		The root zone file can be obtained using methods described at
	<https://www.internic.net/domain/root.zone>.		<https://www.iana.org/domains/root/files>.
	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 d.root-servers.net		o d.root-servers.net
End of changes. 4 change blocks.
	5 lines changed or deleted		5 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/