IETF Logo Mail Archive

Re: [DNSOP] Call for Adoption: draft-toorop-dnsop-dns-catalog-zones

Loganaden Velvindron <loganaden@gmail.com> Wed, 13 May 2020 07:44 UTC

Return-Path: <loganaden@gmail.com>
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 D90B73A0F9A for <dnsop@ietfa.amsl.com>; Wed, 13 May 2020 00:44:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.098
X-Spam-Level:
X-Spam-Status: No, score=-1.098 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, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ciUFZcJS62pU for <dnsop@ietfa.amsl.com>; Wed, 13 May 2020 00:44:27 -0700 (PDT)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (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 6F25B3A0884 for <dnsop@ietf.org>; Wed, 13 May 2020 00:44:27 -0700 (PDT)
Received: by mail-io1-xd34.google.com with SMTP id f3so17007526ioj.1 for <dnsop@ietf.org>; Wed, 13 May 2020 00:44:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JI5ZTZAfImOJRZjngjdzi5+EmEY8i07Q3Eh7Y1sOY3k=; b=OFe1Ptu1qj+7coAps0ShSHsfYd8W0mJoYVbQM4JfwD/VBTSIPd4JbNIhosHth5Qmh4 x4Kz7N8K1zhplcWooLkk94znWxzAQDhuHc56zEKJuUZq/8JmVfoFCP95ULg9QdwCoTU0 2SYfdvodC49deQZdwbK9w27x1MYFi9haMgrrq7OcG7bAmJiIpntY6vwl12q47E1XCW16 KUyIP3jcTvtlq3XeTVc/Q0+7lt+Tmc7oZ7GoDiEHywmBOSx+aw+DfJJ4BJ0ZwozkaZVO nhPnXcw4+zTV3APej0QZ6uRhiPGviQ8gWSromneRLAhFNZqrvM/r4aUimxJNxAGGtnF4 YBbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JI5ZTZAfImOJRZjngjdzi5+EmEY8i07Q3Eh7Y1sOY3k=; b=lVsMC1zl9vLDbiAGXQfYUKWq1pYMzpZ11u/gdOePb+NnAiFhWN+vCd6zG849JJ8n1D M4K6fVT34RYL+NmiUiioFKBtv+0UtDyvEzEGhyZ3vrHfqmSuu0Prlzl5hTwoX2OON6mh kXLG53jyjttQjWsi61eD7yoDBqg2pEvCTujXoWct13mkOUD/v+6qVyMGeyNAltxWZb8J Lc+q63hz1bXtuXIjxQNsrx6u0RzTv1SfwS0UVj5e61mAHZFrC8PoZLQB7XZXH3+Jg/wO n04/nqw4zDrRYuesKxym9wNRLkoocSDNHBnZbGuIiFHmhFcHi+8FhHDzmhnHhWp9E9DM JiDQ==
X-Gm-Message-State: AGi0PuaQd4WtGtSv7zF9Tq5N738Bc4Zn5lrh54y+obCR4avaRJ1m+M9q FPGA7rq/++wFVdAvXZPQPV7HieM2T2WLflkKmM0=
X-Google-Smtp-Source: APiQypLWgQmMUsx+YHO64yERYKrkU9BULepHi0oUl6or7c71qQP+3e8wP63F7T9sfaAtbgD0MTudOpqEaHPNIzeulZA=
X-Received: by 2002:a6b:e911:: with SMTP id u17mr17789805iof.29.1589355866610; Wed, 13 May 2020 00:44:26 -0700 (PDT)
MIME-Version: 1.0
References: <CADyWQ+HHBqFX_GhzuXD5FNwSUHBzeqTy3pWWvz41ZjPhx=2PyQ@mail.gmail.com> <CA+nkc8Bs19J8AsLU0BwtFi5dCHN6CJqkoWY1L=HrdZZJhTeVWQ@mail.gmail.com> <aeb8abe6-bfe0-7ab3-0490-d76633ad5b82@nlnetlabs.nl>
In-Reply-To: <aeb8abe6-bfe0-7ab3-0490-d76633ad5b82@nlnetlabs.nl>
From: Loganaden Velvindron <loganaden@gmail.com>
Date: Wed, 13 May 2020 11:44:15 +0400
Message-ID: <CAOp4FwSP9DfaeKNA-1SfwSJXKA364tBTEaaFXW+y5gPafRjkeg@mail.gmail.com>
To: Willem Toorop <willem@nlnetlabs.nl>
Cc: dnsop <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ICYaphe1gBP8jZHk51OPcYxQcBs>
Subject: Re: [DNSOP] Call for Adoption: draft-toorop-dnsop-dns-catalog-zones
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: Wed, 13 May 2020 07:44:29 -0000

On Tue, May 12, 2020 at 4:50 PM Willem Toorop <willem@nlnetlabs.nl> wrote:
>
> Op 11-05-2020 om 21:38 schreef Bob Harold:
> > On Mon, May 11, 2020 at 1:42 PM Tim Wicinski <tjw.ietf@gmail.com
> > <mailto:tjw.ietf@gmail.com>> wrote:
> >
> >
> >     All,
> >
> >     As we stated in the meeting and in our chairs actions, we're going
> >     to run
> >     regular call for adoptions over next few months.
> >     We are looking for *explicit* support for adoption.
> >
> >
> >     This starts a Call for Adoption for draft-toorop-dnsop-dns-catalog-zones
> >
> >     The draft is available here:
> >     https://datatracker.ietf.org/doc/draft-toorop-dnsop-dns-catalog-zones/
> >
> >     Please review this draft to see if you think it is suitable for adoption
> >     by DNSOP, and comments to the list, clearly stating your view.
> >
> >     Please also indicate if you are willing to contribute text, review, etc.
> >
> >     This call for adoption ends: 25 May 2020
> >
I support Adoption of the document and I'm willing to review it.

> >     Thanks,
> >     tim wicinski
> >     DNSOP co-chair
> >
> >
> > I support adoption and will review.
> >
> > "3.  Description
> > An implementation of catalog zones MAY allow the catalog to contain
> >    other catalog zones as member zones."
> >
> > It seems ok to me to allow catalog zones to include other catalog zones
> > as future feature, although I cannot figure out yet how that would work,
> > but it might conflict with:
> >
> > "6.1.  Implementation Notes
> >    Catalog zones on secondary nameservers would have to be setup
> >    manually"
>
> Thanks Bob,
>
> The secondary has to be "setup manually",
> - to regard the zone to be a catalog zone
> - but also, optionally, to associate a set of configuration which are
>   applied to the zones generated from the catalog.
>
> One of the things in the associated set of configuration could be that
> zones from a certain catalog, are catalog zones themselves, however with
> which set of configuration the zones added from those catalog are
> associated, also needs to be configured manually on the secondaries.
>
> -- Willem
>
> >
> > --
> > Bob Harold
> >
> >
> > _______________________________________________
> > DNSOP mailing list
> > DNSOP@ietf.org
> > https://www.ietf.org/mailman/listinfo/dnsop
> >
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

v2.23.0 | Report a Bug | By Email