IETF Logo Mail Archive

Re: [DNSOP] I-D Action: draft-ietf-dnsop-glue-is-not-optional-04.txt

Ralf Weber <dns@fl1ger.de> Mon, 18 April 2022 08:44 UTC

Return-Path: <dns@fl1ger.de>
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 C4D8E3A09B5 for <dnsop@ietfa.amsl.com>; Mon, 18 Apr 2022 01:44:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24gmEdR5w41v for <dnsop@ietfa.amsl.com>; Mon, 18 Apr 2022 01:44:07 -0700 (PDT)
Received: from smtp.guxx.net (nyx.guxx.net [85.10.208.173]) by ietfa.amsl.com (Postfix) with ESMTP id 626173A09A4 for <dnsop@ietf.org>; Mon, 18 Apr 2022 01:44:06 -0700 (PDT)
Received: from [192.168.42.98] (p54b8a429.dip0.t-ipconnect.de [84.184.164.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by nyx.guxx.net (Postfix) with ESMTPSA id 14B665F402FE; Mon, 18 Apr 2022 08:44:03 +0000 (UTC)
From: Ralf Weber <dns@fl1ger.de>
To: "Wessels, Duane" <dwessels@verisign.com>
Cc: dnsop <dnsop@ietf.org>
Date: Mon, 18 Apr 2022 10:43:50 +0200
X-Mailer: MailMate (1.14r5886)
Message-ID: <AA30A2D8-ED39-4A0C-875A-617A779176B6@fl1ger.de>
In-Reply-To: <B261F0B0-D908-49F3-A277-8DA5ED4E4E9E@verisign.com>
References: <164435963503.4033.12918772667601928806@ietfa.amsl.com> <13032699-D701-436A-8924-D0628B5DD796@verisign.com> <78C5F649-DE06-4D81-BCF0-EEDF33CBC9E3@fl1ger.de> <B261F0B0-D908-49F3-A277-8DA5ED4E4E9E@verisign.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/oKQ2M930g__4pxi8_1zBayS2UeE>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-glue-is-not-optional-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 18 Apr 2022 08:44:10 -0000

Moin!

On 16 Apr 2022, at 0:44, Wessels, Duane wrote:
> Ralf (and others),
>
> how does this look to you?
>
> In other words, this document only makes requirements on "available
> glue records" (i.e., those given in a zone), but does not make
> requirements regarding thier presence in a zone.
Typo here “their presence in a zone”

> If some glue records are absent from a given zone, an authoritative
> name server may be unable to return a useful referral response for
> the corresponding domain. The IETF may want to consider a separate
> update to the requirements for including glue in zone data, beyond
> those given in [@!RFC1034] and [@!RFC1035].
Yeah that looks fine to me. The main point was to make sure that zone
data can also be a cause of failed/false referral. This text addresses
this.

So long
-Ralf
——-
Ralf Weber

v2.8.7 | Report a Bug | By Email