[DNSOP] Re: Working Group Last Call for draft-ietf-dnsop-generalized-notify

Matthijs Mekking <matthijs@pletterpet.nl> Fri, 10 January 2025 09:09 UTC

Return-Path: <matthijs@pletterpet.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 59506C151524 for <dnsop@ietfa.amsl.com>; Fri, 10 Jan 2025 01:09:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=pletterpet.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 IMPqESRgbm9F for <dnsop@ietfa.amsl.com>; Fri, 10 Jan 2025 01:09:20 -0800 (PST)
Received: from outbound7.mail.transip.nl (outbound7.mail.transip.nl [IPv6:2a01:7c8:7c9:ca11:136:144:136:7]) (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 DD0CCC151096 for <dnsop@ietf.org>; Fri, 10 Jan 2025 01:09:18 -0800 (PST)
Received: from submission4.mail.transip.nl (unknown [10.103.8.155]) by outbound7.mail.transip.nl (Postfix) with ESMTP id 4YTwnl6j0jzQvvWW for <dnsop@ietf.org>; Fri, 10 Jan 2025 10:09:15 +0100 (CET)
Received: from [IPV6:2001:500:60:200:8000::28] (unknown [IPv6:2001:500:60:200:8000::28]) by submission4.mail.transip.nl (Postfix) with ESMTPA id 4YTwnk6kd0z2pRDk0 for <dnsop@ietf.org>; Fri, 10 Jan 2025 10:09:14 +0100 (CET)
Message-ID: <fc7b1507-f434-49e4-a4f7-60079a5984f8@pletterpet.nl>
Date: Fri, 10 Jan 2025 10:09:12 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: dnsop@ietf.org
References: <CABf5zv+eqJ4g9oYM6JXyXj3pE9yR=bd9TEffANFzO8ORXHT4sA@mail.gmail.com> <6927bac8-e3ba-450e-ba80-20363b966091@pletterpet.nl> <57565a04-39f7-4731-9cdc-3a3030ec6672@desec.io>
Content-Language: en-US, nl-NL
From: Matthijs Mekking <matthijs@pletterpet.nl>
In-Reply-To: <57565a04-39f7-4731-9cdc-3a3030ec6672@desec.io>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: ClueGetter at submission4.mail.transip.nl
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; s=transip-a; d=pletterpet.nl; t=1736500155; h=from:subject:to: references:in-reply-to:date:mime-version:content-type; bh=xngOXybGv0TYuOWPObuj4wqZojrEBN9sTKCFjL2d2oU=; b=BhaICK2g58xER/Vn1Qm/Z+mPKIcaD2IE2QdTbY+V9NGWATYkEGpw4YhBmIq2zFW+qoMaZC SLtxsMiYVl9W3imi/0wAmhiLoCDDE53gfUGwp4PZL5CBsl2+RhEFKrWs5gd3jXO/wJJNoe 5mK4ygVXvS9KuwcbhIW+xJ20UilnSCPhQlC1Qz5tSEPIIHIYIS9XWXIHua1L8d7dSQyuBu JOIppUho3Tj5xTx1Xys7rI6STk6LJ5smnKvSctDRRnDXzIDf83pDKZoNFTXVX2VbBrd3fG IOdgwffJi548N/Hd8MQ+/JFIho75T/wZBiSoiyKNzo5oZo2GPsxNgj5WVlXyQA==
X-Report-Abuse-To: abuse@transip.nl
Message-ID-Hash: U36ZJAVDYJVSABOEWAOX47LG2E3ZF6CH
X-Message-ID-Hash: U36ZJAVDYJVSABOEWAOX47LG2E3ZF6CH
X-MailFrom: matthijs@pletterpet.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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: Working Group Last Call for draft-ietf-dnsop-generalized-notify
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Q71LRIYk6TmBPKCuw16DubB-M70>
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>

Hi Peter,

On 09-01-2025 21:31, Peter Thomassen wrote:
> Hi Matthijs,
> 
> Thank you for your helpful review! Please find some responses below:
> 
> On 1/9/25 14:09, Matthijs Mekking wrote:
>> Section 3
>> ---------
>> "There MUST NOT be more than one DSYNC record for each combination of 
>> rrtype and scheme."
>>
>> I wonder what the argument is for this. Doesn't this prevent 
>> redundancy and failover for notification targets?
> 
> The argument is that if there are several, then there are several ways 
> to handle that (use all? pick one? try sequentially? which sequence?).
> 
> The question of how to handle this situation was raised in the Dnsdir 
> review [1]. The authors figured that regardless of which strategy is 
> specified, sender implementations would most likely not implement that 
> complexity, but try the "first", and fire and forget. It seemed that 
> simplicity would lead to more reliable operation in this case.
> 
> [1]: 
> https://mailarchive.ietf.org/arch/msg/dnsop/LFsvddryRr-aYM3BTGyo7My1bD0/

Fair enough.

>> 2. "If a DSYNC RRset results, return it."
>>
>> This reads weird. I guess something like "If there is a validated 
>> positive DSYNC answer, return it".
> 
> Fixed. ("If a positive DSYNC answer results, return it.")

Thanks.


>> The example in step 3 uses city.ise.mie.jp, but there are domain names 
>> reserved for documentation purposes ("example.", "example.com.", 
>> "example.net.", "example.org.", and any names falling within those 
>> domains), so let's use one of these for the example.
> 
> Opinions differ; others found that particular example very useful [2].
> 
> We picked this because it is very illustrative, and because the 
> existence of reserved example names does imply that one cannot use other 
> examples. However, we're open to replacing the example; it would be 
> great if you could in this case suggest some text. (I did not manage to 
> come up with one that's equally instructive.)
> 
> [2]: 
> https://mailarchive.ietf.org/arch/msg/dnsop/6NRRI-p4Xsw0p9UVNIGuAuxhqQ0/


I would use city.ise.mie.example instead, unless you have confirmation 
that JPRS is fine with using .jp as an example here.

(Perhaps you picked this domain name because it is a real world case of 
a delegation with empty non-terminals, but it is not guaranteed that 
this will always be the case anyway).

Best regards, Matthijs

> 
> Thanks again,
> Peter + co-authors
>