IETF Logo Mail Archive

Re: [DNSOP] Adoption of new EDNS opcode "rrserial"

Joe Abley <jabley@hopcount.ca> Mon, 10 May 2021 16:55 UTC

Return-Path: <jabley@hopcount.ca>
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 A6AB33A2375 for <dnsop@ietfa.amsl.com>; Mon, 10 May 2021 09:55:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 kXsQmq6nHh3O for <dnsop@ietfa.amsl.com>; Mon, 10 May 2021 09:55:30 -0700 (PDT)
Received: from mail-qv1-xf2c.google.com (mail-qv1-xf2c.google.com [IPv6:2607:f8b0:4864:20::f2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A79033A23BC for <dnsop@ietf.org>; Mon, 10 May 2021 09:55:27 -0700 (PDT)
Received: by mail-qv1-xf2c.google.com with SMTP id jm10so8695898qvb.5 for <dnsop@ietf.org>; Mon, 10 May 2021 09:55:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rxLjIaWzMjHFSKAk0rFvTrqgBSsWxkBmgGPDXXt65k4=; b=aC3jUdOzfX+Pums0oG+UcS+8/hkyRdosgfivLnik5wfnkv1l6upEzth4sO3Yqk4yZp 88Y3gWz+aRwovTDD9diQAYPtqENFsAFxYvHt5Cfr/G05D2weAX+ot97OwIQzzPg7cplD yLHeUIg8EP82HeYvdyKeP1bR4DWYAO/LMX/WU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rxLjIaWzMjHFSKAk0rFvTrqgBSsWxkBmgGPDXXt65k4=; b=ZcYnCy6CPtkrlVTEKCzbns4WmcAmhKXdXvn+VLaNXcs51wiyEpNr+Yr7ZFQRRyM7Bc nAijiqvCXHlXPhjV6tPu3N0NKrFv/1Srl03N53Iukaxd3cCP9LulvuOtUZXp3rT+tFeW PKEomsBdKKVcYZKkQaCHCYWYFobrGBebQsRXb2/cFArIosLumAtKBGbwxnbFTYhZ9+i/ hwTX9admSbYm7dFCEAPau58uJL+blqDr1iBEABewlRIXC66aDzTe5wmSXzuV5kZWXpK3 mYqocEtv86usWrxHpwYTruZAvr467PtbkZxSQ7mRkxCSgai/Sw3ZXrEhR2i/N2wrkHzD jsBw==
X-Gm-Message-State: AOAM530NdqLVYwMRcm7bTh4dPamn128oCI31eYeJEyDyPaUTxK2JtpXv ymX3tIfrYvp983StOAZqckLOpJ3u03wnK5hlhC8=
X-Google-Smtp-Source: ABdhPJzZbFxdOxEdaFTeAzK90KVV04JuJUlp2KPgZNR6fCLHUiwlGyXhaSSgdg6fgBx0cO+ROUr+hw==
X-Received: by 2002:a05:6214:180b:: with SMTP id o11mr24666493qvw.22.1620665724805; Mon, 10 May 2021 09:55:24 -0700 (PDT)
Received: from smtpclient.apple ([2607:f2c0:e784:c7:f88a:8f71:955b:ab3]) by smtp.gmail.com with ESMTPSA id p190sm11858243qke.13.2021.05.10.09.55.23 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 May 2021 09:55:24 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.80.0.2.43\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <9bf26dfa-e798-38c8-e085-dc1f72502bd5@nic.cz>
Date: Mon, 10 May 2021 12:55:22 -0400
Cc: dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D24D1D76-0ED3-422B-96AB-0633D8B60B42@hopcount.ca>
References: <20200127150847.taxhqeipwq6jg2rr@nic.cl> <c15437aa-365b-3a53-1d06-8d33491fb826@isc.org> <9bf26dfa-e798-38c8-e085-dc1f72502bd5@nic.cz>
To: Vladimír Čunát <vladimir.cunat+ietf@nic.cz>
X-Mailer: Apple Mail (2.3654.80.0.2.43)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/bTa44FLYWveXtbbw1Hbyi7F4yaw>
Subject: Re: [DNSOP] Adoption of new EDNS opcode "rrserial"
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, 10 May 2021 16:55:46 -0000

Hi Vladimir,

On 10 May 2021, at 04:32, Vladimír Čunát <vladimir.cunat+ietf@nic.cz> wrote:

> On 10. 05. 21 10:19, Petr Špaček wrote:
>> I think the proper solution should be a real multi-query option, which incidentally provides a superset of RRSERIAL capabilities.
> 
> If multi-queries require the records being in sync (if from the same zone), I really dislike the implications of them being sent to resolvers, especially for many questions at once.  Caching, in particular.

Yes, I agree with that. Perhaps we could specify that a request for an RRSERIAL MUST only be satisfied for a response with AA=1, so that only servers that are able to provide an authoritative response to the original query will return it.

In contrast, I think there are probably use cases for a server that can't provide an authoritative response (e.g. a recursive server) to process a more generic multi-question query. So this seems like a reason to consider the two problem statements separately. I don't know exactly what use cases Petr had in mind for that though, so I'm guessing slightly.


Joe

v2.23.0 | Report a Bug | By Email