IETF Logo Mail Archive

Re: [DNSOP] New Version Notification - draft-ietf-dnsop-dns-catalog-zones-09.txt

Kees Monshouwer <keesm@monshouwer.eu> Wed, 08 February 2023 08:33 UTC

Return-Path: <keesm@monshouwer.eu>
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 1CC83C14F72D; Wed, 8 Feb 2023 00:33:11 -0800 (PST)
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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=monshouwer.eu
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 QJR03KRKmuvD; Wed, 8 Feb 2023 00:33:07 -0800 (PST)
Received: from admin.monshouwer.eu (admin.monshouwer.eu [195.191.112.64]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2E70C14F72F; Wed, 8 Feb 2023 00:33:04 -0800 (PST)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a00:7c80:31:10::51; helo=mailhost.monshouwer.eu; envelope-from=keesm@monshouwer.eu; receiver=<UNKNOWN>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monshouwer.eu; s=default; t=1675845180; bh=YbrHLLll3OCZ+YCf7BQim/D+AmUaFM1PM8Iv6Jlogto=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=TErY0H53l4+F8L8g/viQQbJEurgCL3XwR/Inylx4YHogMMuFM6RMTyV+OR0cokdGc CC4hgtrgmg19JVY36KUqlrjLH8qE5ixC++0aKnFWMNY2fdj541yIA4X0uZwK72dblm ZY6S4kB9DLRuW7YQd8+cCjdik9PMVBMxyRdHGSM64mdAUd14SYeNrQdqpOpubR691T lsWUeQDS+kKUedUzL9+jexgw0AVYeTzA6me7HAqPzXEw9gPRVDmz0VlUKGXt1AYNMB 2eakSnW8fjm0lcrB+0sllmKIzoSNbkZPwbX3gU93FAEcfxy+atjRrPhSakTy52v16Z h0F1u8Ks56Law==
Received: from mailhost.monshouwer.eu (mailhost.monshouwer.eu [IPv6:2a00:7c80:31:10::51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by admin.monshouwer.eu (Postfix) with ESMTPS id EDA04182F897; Wed, 8 Feb 2023 08:33:00 +0000 (UTC)
Received: from [IPV6:2a00:7c80:31:b45e:4a29:2b2d:f035:c217] (unknown [IPv6:2a00:7c80:31:b45e:4a29:2b2d:f035:c217]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailhost.monshouwer.eu (Postfix) with ESMTPSA id AB3A011FC83; Wed, 8 Feb 2023 08:33:00 +0000 (UTC)
Content-Type: multipart/alternative; boundary="------------aOtLggGIr81iSc3SynduVnBM"
Message-ID: <edcd7b0c-e47d-e2bd-8932-d50dbdfd0f23@monshouwer.eu>
Date: Wed, 08 Feb 2023 09:32:59 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1
To: Paul Wouters <paul.wouters=40aiven.io@dmarc.ietf.org>, draft-ietf-dnsop-dns-catalog-zones.authors@ietf.org, "dnsop@ietf.org WG" <dnsop@ietf.org>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, "Murray S. Kucherawy" <superuser@gmail.com>
References: <167577800490.53807.9257358286100121972@ietfa.amsl.com> <CAGL5yWZNzyJWcZ2eLL6Yw0JFNusPQo2AQHr678C8kXGHio4-Lw@mail.gmail.com>
Content-Language: nl, en-GB
From: Kees Monshouwer <keesm@monshouwer.eu>
In-Reply-To: <CAGL5yWZNzyJWcZ2eLL6Yw0JFNusPQo2AQHr678C8kXGHio4-Lw@mail.gmail.com>
X-Virus-Scanned: clamav-milter 0.100.3 at mailhost.monshouwer.eu
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/8wAGYdSXhakF40K7gsmIivDUbXQ>
Subject: Re: [DNSOP] New Version Notification - draft-ietf-dnsop-dns-catalog-zones-09.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 08 Feb 2023 08:33:11 -0000

Hi Paul,

On 2/7/23 16:45, Paul Wouters wrote:
> On Tue, Feb 7, 2023 at 8:53 AM <internet-drafts@ietf.org> wrote:
>
>  Why must a catalog server / zone only support one version at most? Eg 
> if version "3" comes out that would
> add some things, but is backwards compatible with version "2", 
> wouldn't it be useful to be able to have an
> RRset of two RRs, showing it supports both version 2 and 3? Why is 
> there a constraint to only allow at most 1
> version per catalog zone ?

Version is a schema version, not a feature level. As long as new 
features can be added in the same schema no version bump is necessary. 
Since it is impossible to put two incompatible schemas is a single 
catalog zone only one version RR is allowed.

Regards,

Kees Monshouwer

v2.23.0 | Report a Bug | By Email