RFC 9619 on In the DNS, QDCOUNT Is (Usually) One
rfc-editor@rfc-editor.org Wed, 24 July 2024 21:40 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8D62C14CF12; Wed, 24 Jul 2024 14:40:12 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 4B9F07FA60; Wed, 24 Jul 2024 14:40:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9619 on In the DNS, QDCOUNT Is (Usually) One
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240724214012.4B9F07FA60@rfcpa.rfc-editor.org>
Date: Wed, 24 Jul 2024 14:40:12 -0700
Message-ID-Hash: SE4Z36ZT4LKKAINWHSSIWY76BZMKNOAN
X-Message-ID-Hash: SE4Z36ZT4LKKAINWHSSIWY76BZMKNOAN
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dnsop@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/mg2GZ9fkJyQxPxGr15IvLyrES5E>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9619
Title: In the DNS, QDCOUNT Is (Usually) One
Author: R. Bellis,
J. Abley
Status: Standards Track
Stream: IETF
Date: July 2024
Mailbox: ray@isc.org,
jabley@cloudflare.com
Pages: 7
Updates: RFC 1035
I-D Tag: draft-ietf-dnsop-qdcount-is-one-04.txt
URL: https://www.rfc-editor.org/info/rfc9619
DOI: 10.17487/RFC9619
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.
This document is a product of the Domain Name System Operations Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC