Re: [DNSOP] Call for Adoptions: draft-lhotka-dnsop-iana-class-type-yang

Benno Overeinder <benno@NLnetLabs.nl> Fri, 01 November 2019 11:01 UTC

Return-Path: <benno@NLnetLabs.nl>
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 593B012008A for <dnsop@ietfa.amsl.com>; Fri, 1 Nov 2019 04:01:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nlnetlabs.nl
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 HzBkF4qRi91O for <dnsop@ietfa.amsl.com>; Fri, 1 Nov 2019 04:01:18 -0700 (PDT)
Received: from dicht.nlnetlabs.nl (dicht.nlnetlabs.nl [185.49.140.10]) (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 E0D0912004E for <dnsop@ietf.org>; Fri, 1 Nov 2019 04:01:17 -0700 (PDT)
Received: from [192.168.1.10] (j48230.upc-j.chello.nl [24.132.48.230]) by dicht.nlnetlabs.nl (Postfix) with ESMTPSA id 264DF1C052; Fri, 1 Nov 2019 12:01:16 +0100 (CET)
Authentication-Results: dicht.nlnetlabs.nl; dmarc=fail (p=none dis=none) header.from=NLnetLabs.nl
Authentication-Results: dicht.nlnetlabs.nl; spf=fail smtp.mailfrom=benno@NLnetLabs.nl
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1572606076; bh=ZO3jdAMcUa25NAkC7dy6TJiO5R2o0FpPBqM3Jp96hz0=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=kSE0sEOayG5wrAe9WV7GZuVUpDAjcrlMonBs9eZFbmwJCMBr9pg4OfNhAiU/2qMOk pZAwSaQ2+TwVs9brB+gXw2TQUwvjEfilHyXJriaGLIAZEI6mG0Vmk6LLjVn2rvyPQw BTsXXjOu2Rnlgy/kZhLAoYmhABDDIIq4BL18cXGg=
To: 'DNSOP WG' <dnsop@ietf.org>
Cc: Paul Wouters <paul@nohats.ca>, "Normen B. Kowalewski" <nbkowalewski@gmx.net>, 'Ladislav Lhotka' <lhotka@nic.cz>
References: <820fe3a1-9d54-15c1-8194-8a607bdf6a31@NLnetLabs.nl> <87sgqy2azd.fsf@nic.cz> <920E9418-4440-46F6-87B7-68CF8B03C408@gmx.net> <C66220A931BC4753B6818DAF898AE2E8@T1650> <426d8bf2-cf28-11f6-4435-08fcaa37e7f5@NLnetLabs.nl> <alpine.LRH.2.21.1910071329420.19930@bofh.nohats.ca>
From: Benno Overeinder <benno@NLnetLabs.nl>
Openpgp: preference=signencrypt
Message-ID: <41c0d828-b8c0-8788-483a-144fca921357@NLnetLabs.nl>
Date: Fri, 1 Nov 2019 12:01:16 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <alpine.LRH.2.21.1910071329420.19930@bofh.nohats.ca>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/EdOabxDHxkx5uBy4xNF5XoxyGBA>
Subject: Re: [DNSOP] Call for Adoptions: draft-lhotka-dnsop-iana-class-type-yang
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, 01 Nov 2019 11:01:19 -0000

On 10/7/19 7:31 PM, Paul Wouters wrote:
> On Mon, 7 Oct 2019, Benno Overeinder wrote:
> 
>> Questions to WG:
>>
>> 1) iana-class-type-yang document to OPSAWG?
> 
> I would assume most people here will the same about the document,
> wherever it is discussed ? So this option seems odd.
> 
>> 2) follow-up work on YANG data models for DNS servers in DNSOP?
> 
> Speaking for myself, as long as we are not populating RFCs with
> obsoleted DNS data or just create RFC with copies of IANA registries,
> I'm fine with helping on a document. But not if it is a blind copy
> and paste from IANA (whether at DNSOP or OPSAWG)

After also consulting our AD, we decided to keep the document in DNSOP WG.

After the WG call for adoption on the mailing list (normal procedure),
we also want to ask the WG during the meeting in Singapore to raise
their hands and volunteer for helping the document and for review.  We
want to ensure that enough people in the DNSOP WG are committed to
working on the document.

Thanks,

-- Benno