IETF Logo Mail Archive

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

Paul Wouters <paul@nohats.ca> Mon, 07 October 2019 17:31 UTC

Return-Path: <paul@nohats.ca>
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 43BB8120178 for <dnsop@ietfa.amsl.com>; Mon, 7 Oct 2019 10:31:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 ai7dX0WA0vgZ for <dnsop@ietfa.amsl.com>; Mon, 7 Oct 2019 10:31:42 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 8FCC4120180 for <dnsop@ietf.org>; Mon, 7 Oct 2019 10:31:42 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 46n6wX2kCvzFLb; Mon, 7 Oct 2019 19:31:40 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1570469500; bh=ilDxOFqxw4dA2htreVu9O5V7I8zfGy5Z8JXBUHBsPwc=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=Ht4SFOsVbEjInCPXKEFnO7LHEu4td3lfebcGAguFiMIqIyDSANFr6lEanl/clssrr 8ImE+xYs8bOsdvM8KUDvyRyXYVFtiC1Ff+DB7v5eD51ck3fcKpokPo5C5o3o2YIPL6 FfIaJ1dnfxjYsw0vXiA3hwOUcLmUqY+unGSsAYO4=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id xIIO5hpgRcvy; Mon, 7 Oct 2019 19:31:39 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Mon, 7 Oct 2019 19:31:39 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 7FAC318CA2; Mon, 7 Oct 2019 13:31:38 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 7FAC318CA2
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 75D4A41349CA; Mon, 7 Oct 2019 13:31:38 -0400 (EDT)
Date: Mon, 07 Oct 2019 13:31:38 -0400
From: Paul Wouters <paul@nohats.ca>
To: Benno Overeinder <benno@NLnetLabs.nl>
cc: "Normen B. Kowalewski" <nbkowalewski@gmx.net>, 'Ladislav Lhotka' <lhotka@nic.cz>, 'DNSOP WG' <dnsop@ietf.org>
In-Reply-To: <426d8bf2-cf28-11f6-4435-08fcaa37e7f5@NLnetLabs.nl>
Message-ID: <alpine.LRH.2.21.1910071329420.19930@bofh.nohats.ca>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/TqRaEVlVnfgsqudeN3ydF8UOEIE>
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: Mon, 07 Oct 2019 17:31:44 -0000

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)

Paul

v2.23.0 | Report a Bug | By Email