IETF Logo Mail Archive

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

Joe Abley <jabley@hopcount.ca> Fri, 07 May 2021 18:09 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 1E2023A2C72 for <dnsop@ietfa.amsl.com>; Fri, 7 May 2021 11:09:37 -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 9VInxS6T-wIq for <dnsop@ietfa.amsl.com>; Fri, 7 May 2021 11:09:32 -0700 (PDT)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (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 212653A2C75 for <dnsop@ietf.org>; Fri, 7 May 2021 11:09:31 -0700 (PDT)
Received: by mail-qt1-x835.google.com with SMTP id g13so7248922qts.4 for <dnsop@ietf.org>; Fri, 07 May 2021 11:09:31 -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=I5Or+TAwLCJoA4UKh9DT/ONhqA18WOWBQSriN70aSYg=; b=B1uRWKof55b4HSxP+1XYzvEhpjIfL1QzVR8laIgBOcCB/6z3b5ekfhOrSqs+mI+84S 2QdR08+EdjUDjNl/RWdEZaU4vqVYNdVMgmbfWcHXMaDgtg6rX3VTeR5/rjy60V78f82b auH0lBmIgmtRGWtIpVwjwWqovobrQTSr7n87k=
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=I5Or+TAwLCJoA4UKh9DT/ONhqA18WOWBQSriN70aSYg=; b=dfJ0ziyXFZXv/llEcds5WTtiCG+qauKTcd4HyVMc6Gaok7g4Kqv+wgrQPIm3F5WKhH k0BryjFmdInd9IpSw/xaU9dRx8cCH25LWbOl+J+ckfSKO8ZbBIeNlNUfI2MGlJ6FHCpN P3SzZV90yeBkLDzF4wRszIEqaohnc/Kwn75J5pS8MhiEsKxvRbqdYbxC7+0YNh8Iv2Qa 58PHwACEb6X7rGB3M0tFfyzaW7Dtn/m5udixxxk+BiVtGwu5rfjlINBITpz+F4R+Q7Hy 68/ioJ9DCGbXpkI8f0HvxnAvd8WiLY3LgouGvt7unZQJ2HYP4GgpITNMncXNREsvgLoR Ye0w==
X-Gm-Message-State: AOAM531DiI9uz/4cxbqv8VUInaidP/RRoH+ETeLSm7zStGSdMYTYx9pW v8FQsa37pLhlutoJnE0Whfyo4A==
X-Google-Smtp-Source: ABdhPJwLB7V62dtYy4u3o5FhEAaZi4msaHuTw6gNMHGw803tx1w0q2UdndePQZ+HHhovk9ELVHSA9g==
X-Received: by 2002:a05:622a:1cc:: with SMTP id t12mr10363877qtw.153.1620410969647; Fri, 07 May 2021 11:09:29 -0700 (PDT)
Received: from smtpclient.apple ([2607:f2c0:e784:c7:9de4:d669:ff67:40b1]) by smtp.gmail.com with ESMTPSA id r8sm5092481qtc.24.2021.05.07.11.09.28 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 May 2021 11:09:28 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.80.0.2.43\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <20210507173957.90C147221D3@ary.qy>
Date: Fri, 07 May 2021 14:09:27 -0400
Cc: dnsop@ietf.org, hsalgado@nic.cl
Content-Transfer-Encoding: quoted-printable
Message-Id: <39B9763D-BFD9-4BCE-9FAF-8547DC70D428@hopcount.ca>
References: <20210507173957.90C147221D3@ary.qy>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3654.80.0.2.43)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/IzPCVpqsKM8BzL8YsOr_iYJ7mT0>
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: Fri, 07 May 2021 18:09:37 -0000

On 7 May 2021, at 13:39, John Levine <johnl@taugh.com> wrote:

> It appears that Hugo Salgado  <hsalgado@nic.cl> said:
>> -=-=-=-=-=-
>> 
>> I'll upload a new version to revive it, and ask for a slot
>> in IETF111 for further discussion!
> 
> It looks like it's worth considering, but I also wonder how
> relevant it is for DNS servers that don't use AXFR/IXFR and SOA
> serial numbers to keep versions in sync.

SOA serial numbers are definitely useful for the apex SOA/IN queries that are prerequisites to zone transfers. However, they're also really useful information for any dynamic zone that you're trying to troubleshoot. Successive queries are not necessarily going to return matching information.

By analogy, you can send a query to a nameserver and get a troublesome response, and debug with a HOSTNAME.BIND/CH/TXT query to see what server it was. But for a nameserver provisioned with anycast or as part of a cluster, those data points are not necessarily going to match, which is why NSID is good.


Joe

v2.23.0 | Report a Bug | By Email