[DNSOP] Re: Mahesh Jethanandani's No Objection on draft-ietf-dnsop-rfc8109bis-06: (with COMMENT)
Joe Abley <jabley@strandkip.nl> Tue, 20 August 2024 07:21 UTC
Return-Path: <jabley@strandkip.nl>
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 B1277C14F6B7 for <dnsop@ietfa.amsl.com>; Tue, 20 Aug 2024 00:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strandkip.nl
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 ffMPoY6MRHl5 for <dnsop@ietfa.amsl.com>; Tue, 20 Aug 2024 00:21:10 -0700 (PDT)
Received: from st43p00im-ztfb10061701.me.com (st43p00im-ztfb10061701.me.com [17.58.63.172]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D05DBC14F6B5 for <dnsop@ietf.org>; Tue, 20 Aug 2024 00:21:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=strandkip.nl; s=sig1; t=1724138026; bh=KQwk4hIlmVwGOIoaELPTWfYy72SuRC+DMLQSFsX+lO8=; h=Content-Type:Mime-Version:Subject:From:Date:Message-Id:To; b=NjbdBDoo6FF+G3nkJGtQ8TNz90O474OmAoKWUpN3iOzheREOU3likJGvSP2t4aBzj rZ7vIKkeaPxb/ezpE4tMzftLjcr34YyjsnekI6vQ4dPqqkjTvM18OS/Ux/z/mkoziI GpGmChhxlI1RSw1ivoKTKBcOpPfTqXhLwJR4ODdtGo+jZLHlFD980QD1omib4MOLRc tFqD81QQDpOBdmzGVC+JZ1GuZig56jDbk+pfxxSs8arRvMNFXQWQUdGa/034nxYWAn hhJjoUYCkUJ6WhmJsI8htxIlnTfpobWqdWAN0MbS+bRmjKFUsCqJ8CITADX3ONsQMi dW9Ktr2RTDNcQ==
Received: from smtpclient.apple (st43p00im-dlb-asmtp-mailmevip.me.com [17.42.251.41]) by st43p00im-ztfb10061701.me.com (Postfix) with ESMTPSA id 93AC6380151; Tue, 20 Aug 2024 07:13:43 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\))
From: Joe Abley <jabley@strandkip.nl>
In-Reply-To: <172411432643.2016651.8916400716788212630@dt-datatracker-6df4c9dcf5-t2x2k>
Date: Tue, 20 Aug 2024 09:13:30 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2648CABF-4334-48D5-8ACA-EEA58FAD5467@strandkip.nl>
References: <172411432643.2016651.8916400716788212630@dt-datatracker-6df4c9dcf5-t2x2k>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
X-Mailer: Apple Mail (2.3776.700.51)
X-Proofpoint-GUID: OvtRri3Omjg3T_07vyOeG2ycCYaQr48b
X-Proofpoint-ORIG-GUID: OvtRri3Omjg3T_07vyOeG2ycCYaQr48b
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.1039,Hydra:6.0.680,FMLib:17.12.28.16 definitions=2024-08-19_16,2024-08-19_03,2024-05-17_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 phishscore=0 mlxlogscore=999 spamscore=0 mlxscore=0 clxscore=1030 suspectscore=0 bulkscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2308100000 definitions=main-2408200052
Message-ID-Hash: MBHZ4RZ4CRWRKUSPPZHDSLETFTBPH6HB
X-Message-ID-Hash: MBHZ4RZ4CRWRKUSPPZHDSLETFTBPH6HB
X-MailFrom: jabley@strandkip.nl
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: The IESG <iesg@ietf.org>, draft-ietf-dnsop-rfc8109bis@ietf.org, dnsop-chairs <dnsop-chairs@ietf.org>, dnsop@ietf.org, tjw.ietf@gmail.com
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [DNSOP] Re: Mahesh Jethanandani's No Objection on draft-ietf-dnsop-rfc8109bis-06: (with COMMENT)
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/l5eu-WWPCpkoa_HJTbF4dULwGQ8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>
On Aug 20, 2024, at 02:38, Mahesh Jethanandani via Datatracker <noreply@ietf.org> wrote: > I am not a DNS expert, and was wondering if there is a definition for > "recursive resolvers", and if not, can it be defined here? The idea would be to > understand how they are different from other kinds of resolvers such as > "Designated Resolvers". At the same time, the term "recursive name server" > seems to be used interchangeably with "recursive resolver". Are they the same? (Not an author, just a bystander) "Recursive Resolver" and a host of related terms are defined in RFC 9499. The phrase "recursive name server" colloquially means the same thing, but I thiink it would be reasonable to suggest that this document chooses one term and sticks with it. RFC 9499 quotes the use of "recursive name server" (e.g. in the context of a "security-aware recursive name server") but doesn't offerthe phrase as a synonym for recursive resolver, which is defined. This could probably be improved in a future 9499 replacement. In section 1.2, I suggest: OLD: See [RSSAC026v2] for terminology that relates to the root server system. NEW: See [RFC9499] for terminology that relates to the domain name system in general. See [RSSAC026v2] for terminology that relates to the root server system in particular. Joe
- [DNSOP] Re: Mahesh Jethanandani's No Objection on… Joe Abley
- [DNSOP] Mahesh Jethanandani's No Objection on dra… Mahesh Jethanandani via Datatracker