API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 9619
[ACTIVE]

In the DNS, QDCOUNT Is (Usually) One

Metadata

Publisher
IETF
Doc Type
Standard
Pages
7
Abstract
This document updates RFC 1035 by constraining the allowed value of the QDCOUNT parameter in DNS messages with OPCODE = 0 (QUERY) to a maximum of one, and it specifies the required behavior when values that are not allowed are encountered.
Publication Date
2024-07-01
Status Note
Proposed Standard
DOI
10.17487/RFC9619
Link
https://doi.org/10.17487/RFC9619
Author(s)
Ray Bellis
Joe Abley
Latest version of IETF RFC 9619

Document Versions — IETF RFC 9619

  • ▶ IETF RFC 9619 (2024-07-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC9619.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 9619, In the DNS, QDCOUNT Is (Usually) One. Available at https://doi.org/10.17487/RFC9619
Snippet:
IETF RFC 9619, In the DNS, QDCOUNT Is (Usually) One. Available at https://doi.org/10.17487/RFC9619

HTML (ISO 690 compliant)

Preview:
IETF RFC 9619, In the DNS, QDCOUNT Is (Usually) One. Available at https://doi.org/10.17487/RFC9619
Snippet:
<span class="citation"><cite>IETF RFC 9619</cite>, In the DNS, QDCOUNT Is (Usually) One. Available at <a href="https://doi.org/10.17487/RFC9619" target="_blank" rel="noopener">https://doi.org/10.17487/RFC9619</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 9619, In the DNS, QDCOUNT Is (Usually) One
doi: 10.17487/RFC9619
url: https://doi.org/10.17487/RFC9619
Snippet:
<li>
<cite id="bib-rfc9619">IETF RFC 9619</cite>, In the DNS, QDCOUNT Is (Usually) One
<span class="doi">10.17487/RFC9619</span>
</li>