< draft-ietf-dnsop-edns-chain-query-00.txt		draft-ietf-dnsop-edns-chain-query-01.txt >
	dnsop P. Wouters		dnsop P. Wouters
	Internet-Draft Red Hat		Internet-Draft Red Hat
	Intended status: Standards Track April 11, 2014		Intended status: Standards Track October 27, 2014
	Expires: October 13, 2014		Expires: April 30, 2015
	Chain Query requests in DNS		Chain Query requests in DNS
	draft-ietf-dnsop-edns-chain-query-00		draft-ietf-dnsop-edns-chain-query-01
	Abstract		Abstract
	This document defines an EDNS0 extension that can be used by a DNSSEC		This document defines an EDNS0 extension that can be used by a DNSSEC
	enabled Recursive Nameserver configured as a forwarder to send a		enabled Recursive Nameserver configured as a forwarder to send a
	single DNS query requesting to receive a complete validation path		single DNS query requesting to receive a complete validation path
	along with the regular DNS answer, without the need to rapid-fire		along with the regular DNS answer, without the need to rapid-fire
	many UDP requests in an attempt to attain a low latency.		many UDP requests in an attempt to attain a low latency.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 34 ¶
	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 October 13, 2014.		This Internet-Draft will expire on April 30, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2014 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 14, line 17 ¶		skipping to change at page 14, line 17 ¶
	11. Acknowledgements		11. Acknowledgements
	Andrew Sullivan pointed out that we do not need any new data formats		Andrew Sullivan pointed out that we do not need any new data formats
	to support DNS chains. Olafur Gudmundsson ensured the RRsets are		to support DNS chains. Olafur Gudmundsson ensured the RRsets are
	returned in the proper Sections.		returned in the proper Sections.
	12. Normative References		12. Normative References
	[EASTLAKE-COOKIES]		[EASTLAKE-COOKIES]
	Eastlake, Donald., "Domain Name System (DNS) Cookies",		Eastlake, Donald., "Domain Name System (DNS) Cookies",
	draft-eastlake-dnsext-cookies (work in progress), January		draft-eastlake-dnsext-cookies (work in progress), October
	2014.		2014.
	[RFC1034] Mockapetris, P., "Domain names - concepts and facilities",		[RFC1034] Mockapetris, P., "Domain names - concepts and facilities",
	STD 13, RFC 1034, November 1987.		STD 13, RFC 1034, November 1987.
	[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, November 1987.
	[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, March 1997.
	skipping to change at page 15, line 14 ¶		skipping to change at page 15, line 14 ¶
	[RFC6891] Damas, J., Graff, M., and P. Vixie, "Extension Mechanisms		[RFC6891] Damas, J., Graff, M., and P. Vixie, "Extension Mechanisms
	for DNS (EDNS(0))", STD 75, RFC 6891, April 2013.		for DNS (EDNS(0))", STD 75, RFC 6891, April 2013.
	[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running		[RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
	Code: The Implementation Status Section", RFC 6982, July		Code: The Implementation Status Section", RFC 6982, July
	2013.		2013.
	[TCP-KEEPALIVE]		[TCP-KEEPALIVE]
	Wouters, P., "The edns-tcp-keepalive EDNS0 Option", draft-		Wouters, P., "The edns-tcp-keepalive EDNS0 Option", draft-
	ietf-dnsop-edns-tcp-keeaplive (work in progress), April		ietf-dnsop-edns-tcp-keeaplive (work in progress), October
	2014.		2014.
	Author's Address		Author's Address
	Paul Wouters		Paul Wouters
	Red Hat		Red Hat
	Email: pwouters@redhat.com		Email: pwouters@redhat.com
End of changes. 5 change blocks.
	6 lines changed or deleted		6 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/