< draft-wkumari-dnsop-multiple-responses-01.txt		draft-wkumari-dnsop-multiple-responses-02.txt >
	dnsop W. Kumari		dnsop W. Kumari
	Internet-Draft Google		Internet-Draft Google
	Intended status: Standards Track Z. Yan		Intended status: Standards Track Z. Yan
	Expires: January 07, 2016 CNNIC		Expires: July 8, 2016 CNNIC
	W. Hardaker		W. Hardaker
	Parsons, Inc.		Parsons, Inc.
	July 06, 2015		January 05, 2016
	Returning multiple answers in DNS responses.		Returning multiple answers in DNS responses.
	draft-wkumari-dnsop-multiple-responses-01		draft-wkumari-dnsop-multiple-responses-02
	Abstract		Abstract
	This document (re)introduces the ability to provide multiple answers		This document (re)introduces the ability to provide multiple answers
	in a DNS response.		in a DNS response.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	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 January 07, 2016.		This Internet-Draft will expire on July 8, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2016 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
	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 2, line 23 ¶		skipping to change at page 2, line 23 ¶
	5.1. File Format . . . . . . . . . . . . . . . . . . . . . . . 5		5.1. File Format . . . . . . . . . . . . . . . . . . . . . . . 5
	5.2. Wire Format . . . . . . . . . . . . . . . . . . . . . . . 5		5.2. Wire Format . . . . . . . . . . . . . . . . . . . . . . . 5
	6. Signaling support . . . . . . . . . . . . . . . . . . . . . . 6		6. Signaling support . . . . . . . . . . . . . . . . . . . . . . 6
	7. Stub-Resolver Considerations . . . . . . . . . . . . . . . . 6		7. Stub-Resolver Considerations . . . . . . . . . . . . . . . . 6
	8. Use of Additional information . . . . . . . . . . . . . . . . 6		8. Use of Additional information . . . . . . . . . . . . . . . . 6
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
	10. Security Considerations . . . . . . . . . . . . . . . . . . . 7		10. Security Considerations . . . . . . . . . . . . . . . . . . . 7
	11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7		11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
	12. References . . . . . . . . . . . . . . . . . . . . . . . . . 7		12. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
	12.1. Normative References . . . . . . . . . . . . . . . . . . 7		12.1. Normative References . . . . . . . . . . . . . . . . . . 7
	12.2. Informative References . . . . . . . . . . . . . . . . . 7		12.2. Informative References . . . . . . . . . . . . . . . . . 8
	Appendix A. Changes / Author Notes. . . . . . . . . . . . . . . 8		Appendix A. Changes / Author Notes. . . . . . . . . . . . . . . 8
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
	1. Introduction		1. Introduction
	Often the name being resolved in the DNS provides information about		Often the name being resolved in the DNS provides information about
	why the name is being resolved, allowing the authoritative name		why the name is being resolved, allowing the nameserver to predict
	server operator to predict what other answers the client will soon		what other answers the client will soon query for. By providing
	query for. By providing multiple answers in the response, an		multiple answers in the response, the authoritative name server
	authoritative name server operator can ensure that the recursive		operator can ensure that the recursive server that the client is
	server that the client is using has all the answers in its cache.		using has all the answers in its cache.
	For example, the name server operator of Example Widgets, Inc		For example, the name server operator of Example Widgets, Inc
	(example.com) knows that the example.com web page at www.example.com		(example.com) knows that the example.com web page at www.example.com
	contains various other resources, including some images (served from		contains various other resources, including some images (served from
	images.example.com), some Cascading Style Sheets (served from		images.example.com), some Cascading Style Sheets (served from
	css.example.com) and some JavaScript (data.example.com). A client		css.example.com) and some JavaScript (data.example.com). A client
	attempting to resolve www.example.com is very likely to be a web		attempting to resolve www.example.com is very likely to be a web
	browser rendering the page and so will need to also resolve all of		browser rendering the page and so will need to also resolve all of
	the other names to obtain these other resources. Providing all of		the other names to obtain these other resources. Providing all of
	these answers in response to a query for www.example.com allows the		these answers in response to a query for www.example.com allows the
	skipping to change at page 5, line 49 ¶		skipping to change at page 5, line 49 ¶
	opportunistically returning bar when queried for foo. This		opportunistically returning bar when queried for foo. This
	functionality could also be included in the authoritative name server		functionality could also be included in the authoritative name server
	software itself, but discussions of these re outside the scope of		software itself, but discussions of these re outside the scope of
	this document.		this document.
	5.2. Wire Format		5.2. Wire Format
	The wire format of the Additional RR is the same as the wire format		The wire format of the Additional RR is the same as the wire format
	for a TXT RR:		for a TXT RR:
	+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+		+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
	/ TXT-DATA /		/ TXT-DATA /
	+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+		+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
	Where TXT-DATA is one or more charter-strings.		Where TXT-DATA is one or more charter-strings.
	The Additional RR has RR type TBD [RFC Editor: insert the IANA		The Additional RR has RR type TBD [RFC Editor: insert the IANA
	assigned value and delete this note]		assigned value and delete this note]
	6. Signaling support		6. Signaling support
	Iterative nameservers that support Additional records signal this by		Iterative nameservers that support Additional records signal this by
	setting the OPT record's PL ("plus") bit (bit NN [TBD: assigned by		setting the OPT record's PL ("plus") bit (bit NN [TBD: assigned by
	skipping to change at page 7, line 30 ¶		skipping to change at page 7, line 30 ¶
	cache poisoning (I hope :-))		cache poisoning (I hope :-))
	11. Acknowledgements		11. Acknowledgements
	The authors wish to thank some folk.		The authors wish to thank some folk.
	12. References		12. References
	12.1. Normative References		12.1. Normative References
			[Ref.Bellovin]
			Bellovin, S., "Using the Domain Name System for System
			Break-Ins", 1995,
			<https://www.cs.columbia.edu/~smb/papers/dnshack.pdf>.
	[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, DOI 10.17487/RFC1034, November 1987,
			<http://www.rfc-editor.org/info/rfc1034>.
	[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>.
	[RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS		[RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS
	Specification", RFC 2181, July 1997.		Specification", RFC 2181, DOI 10.17487/RFC2181, July 1997,
			<http://www.rfc-editor.org/info/rfc2181>.
	[RFC5395] Eastlake, D., "Domain Name System (DNS) IANA
	Considerations", RFC 5395, November 2008.
	[Ref.Bellovin]		[RFC5395] Eastlake 3rd, D., "Domain Name System (DNS) IANA
	Bellovin, S., "Using the Domain Name System for System		Considerations", RFC 5395, DOI 10.17487/RFC5395, November
	Break-Ins", 1995, <https://www.cs.columbia.edu/~smb/papers		2008, <http://www.rfc-editor.org/info/rfc5395>.
	/dnshack.pdf>.
	12.2. Informative References		12.2. Informative References
	[I-D.ietf-sidr-iana-objects]		[I-D.ietf-sidr-iana-objects]
	Manderson, T., Vegoda, L., and S. Kent, "RPKI Objects		Manderson, T., Vegoda, L., and S. Kent, "RPKI Objects
	issued by IANA", draft-ietf-sidr-iana-objects-03 (work in		issued by IANA", draft-ietf-sidr-iana-objects-03 (work in
	progress), May 2011.		progress), May 2011.
	Appendix A. Changes / Author Notes.		Appendix A. Changes / Author Notes.
End of changes. 13 change blocks.
	24 lines changed or deleted		29 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/