IETF Logo Mail Archive

Re: [DNSOP] Call for Adoption: draft-salgado-dnsop-rrserial

Hugo Salgado <hsalgado@nic.cl> Tue, 01 June 2021 14:06 UTC

Return-Path: <hsalgado@nic.cl>
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 6C9BE3A1914 for <dnsop@ietfa.amsl.com>; Tue, 1 Jun 2021 07:06:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001] 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 rBYmBXNu1OBs for <dnsop@ietfa.amsl.com>; Tue, 1 Jun 2021 07:05:59 -0700 (PDT)
Received: from mail.nic.cl (mail.nic.cl [IPv6:2001:1398:1::6008]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20FC33A1912 for <dnsop@ietf.org>; Tue, 1 Jun 2021 07:05:59 -0700 (PDT)
Received: from mail.nic.cl (localhost [127.0.0.1]) by mail.nic.cl (Postfix) with ESMTP id 15E2F195D6E30; Tue, 1 Jun 2021 10:05:55 -0400 (-04)
Received: from pepino (unknown [190.163.103.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.nic.cl (Postfix) with ESMTPSA id F2E30195D6E0A; Tue, 1 Jun 2021 10:05:54 -0400 (-04)
Date: Tue, 01 Jun 2021 10:05:53 -0400
From: Hugo Salgado <hsalgado@nic.cl>
To: Peter van Dijk <peter.van.dijk@powerdns.com>
Cc: dnsop@ietf.org
Message-ID: <20210601140553.GA68051@pepino>
References: <CADyWQ+F9Q2mT3cK8MQ-y7pbUm+qhK22CjVkc3i3mtpjHs6mKmw@mail.gmail.com> <20210531161502.GA3679@pepino> <618cefb1-cc91-ba64-8959-0ffe92297991@time-travellers.org> <bbdc3244c047a2738a85ebad8deba3889bec1c64.camel@powerdns.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="gKMricLos+KVdGMg"
Content-Disposition: inline
In-Reply-To: <bbdc3244c047a2738a85ebad8deba3889bec1c64.camel@powerdns.com>
X-Virus-Scanned: ClamAV using ClamSMTP on Tue Jun 1 10:05:55 2021 -0400 (-04) (mail.nic.cl)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/SaC88t9cynjhtxevLMkwHoqDvM4>
Subject: Re: [DNSOP] Call for Adoption: draft-salgado-dnsop-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: Tue, 01 Jun 2021 14:06:06 -0000

On 13:20 01/06, Peter van Dijk wrote:
> On Tue, 2021-06-01 at 08:59 +0200, Shane Kerr wrote:
> > And maybe cache the value if desired?
> 
> I'm already looking forward to having serials in resolver cache dumps!
> 
> > At the very least, maybe the draft should be agnostic towards 
> > non-authoritative servers?
> > 
> > So instead of:
> > 
> >     This EDNS option is aimed only to authorative servers for a zone.
> >     Resolvers and forwarders should ignore the option.  It's only
> >     intended for hop-to-hop communication (not transitive).
> > 
> > Maybe:
> > 
> >     This EDNS option is aimed only at authoritative servers for a zone.
> >     It's only intended for hop-to-hop communication (not transitive).
> >     Resolver and forwarder behavior is undefined.
> 
> I like this. I suspect defining it well for answers from resolvers to
> clients would open up a big can of worms that could kill the draft,
> like many other drafts that have been crushed under the sheer weight of
> scope creep.
> 

Yes, fair enough. Furthermore, the draft currently avoids talking about
"client" and uses "querier", which from the authoritative point of view
could be a debugging human or a resolver.

Hugo

v2.23.0 | Report a Bug | By Email