rfc9619v2.txt		rfc9619.txt
	skipping to change at line 64 ¶		skipping to change at line 64 ¶
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	7.2. Informative References		7.2. Informative References
	Appendix A. Guidance for the Use of QDCOUNT in the DNS		Appendix A. Guidance for the Use of QDCOUNT in the DNS
	Specification		Specification
	A.1. OPCODE = 0 (QUERY) and 1 (IQUERY)		A.1. OPCODE = 0 (QUERY) and 1 (IQUERY)
	A.2. OPCODE = 4 (NOTIFY)		A.2. OPCODE = 4 (NOTIFY)
	A.3. OPCODE = 5 (UPDATE)		A.3. OPCODE = 5 (UPDATE)
	A.4. OPCODE = 6 (DNS Stateful Operations, DSO)		A.4. OPCODE = 6 (DNS Stateful Operations, DSO)
	A.5. Conclusion		A.5. Conclusion
	Acknowledgements		Acknowledgements
	Authors' Addresses		Authors' Addresses
	1. Introduction		1. Introduction
	The DNS protocol [RFC1034] [RFC1035] includes a parameter QDCOUNT in		The DNS protocol [RFC1034] [RFC1035] includes a parameter QDCOUNT in
	the DNS message header whose value is specified to mean the number of		the DNS message header whose value is specified to mean the number of
	questions in the Question section of a DNS message.		questions in the Question section of a DNS message.
	In a general sense, it seems perfectly plausible for the QDCOUNT		In a general sense, it seems perfectly plausible for the QDCOUNT
	parameter, an unsigned 16-bit value, to take a considerable range of		parameter, an unsigned 16-bit value, to take a considerable range of
End of changes. 1 change blocks.
	1 lines changed or deleted		1 lines changed or added
This html diff was produced by rfcdiff 1.48.