[DNSOP] RFC 9471 on DNS Glue Requirements in Referral Responses
rfc-editor@rfc-editor.org Sat, 30 September 2023 15:53 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37BCAC14CE22; Sat, 30 Sep 2023 08:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.468
X-Spam-Level:
X-Spam-Status: No, score=-4.468 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yxnyZLAcy_0x; Sat, 30 Sep 2023 08:53:20 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (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 833F8C14F736; Sat, 30 Sep 2023 08:53:20 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 53CE57633A; Sat, 30 Sep 2023 08:53:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dnsop@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230930155320.53CE57633A@rfcpa.amsl.com>
Date: Sat, 30 Sep 2023 08:53:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/bNWBzKbWKMrNfIbJN_liBKmppTs>
Subject: [DNSOP] RFC 9471 on DNS Glue Requirements in Referral Responses
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Sep 2023 15:53:24 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9471
Title: DNS Glue Requirements in Referral
Responses
Author: M. Andrews,
S. Huque,
P. Wouters,
D. Wessels
Status: Standards Track
Stream: IETF
Date: September 2023
Mailbox: marka@isc.org,
shuque@gmail.com,
paul.wouters@aiven.io,
dwessels@verisign.com
Pages: 9
Updates: RFC 1034
I-D Tag: draft-ietf-dnsop-glue-is-not-optional-09.txt
URL: https://www.rfc-editor.org/info/rfc9471
DOI: 10.17487/RFC9471
The DNS uses glue records to allow iterative clients to find the
addresses of name servers that are contained within a delegated zone.
Authoritative servers are expected to return all available glue
records for in-domain name servers in a referral response. If message
size constraints prevent the inclusion of all glue records for
in-domain name servers, the server must set the TC (Truncated) flag
to inform the client that the response is incomplete and that the
client should use another transport to retrieve the full response.
This document updates RFC 1034 to clarify correct server behavior.
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