On Wed, Feb 8, 2023 at 3:33 AM Kees Monshouwer <keesm=
40monshouwer...@dmarc.ietf.org> wrote:
> Hi Paul,
>
> On 2/7/23 16:45, Paul Wouters wrote:
>
> On Tue, Feb 7, 2023 at 8:53 AM <internet-dra...@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.
>
Ah yes, thanks.
While re-reading the properties / version bits, I noticed this text in
section 4.3.2.1:
In this scenario, consumer(s) shall, by agreement, not sign the
member zone "example.com." with DNSSEC.
Since the "nodnssec" got removed, this sentence makes no more sense to me.
How does the example "show" the
meaning of "not sign the member zone" ?
Paul
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
