IETF Logo Mail Archive

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-iana-class-type-yang

Paul Wouters <paul@nohats.ca> Thu, 15 October 2020 19:11 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 81FC13A131A for <dnsop@ietfa.amsl.com>; Thu, 15 Oct 2020 12:11:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 BZfuh4sMybwq for <dnsop@ietfa.amsl.com>; Thu, 15 Oct 2020 12:11:35 -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 421353A1340 for <dnsop@ietf.org>; Thu, 15 Oct 2020 12:11:29 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4CBzR35qZKzFBj; Thu, 15 Oct 2020 21:11:27 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1602789087; bh=D7SIhDXiVlZbjhA5WDeoO0QcFnjCUF6sZ4XePu9VuEE=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=pqE/1f+e+XEsmbVM48qRey5MPQjqjuEEmENuAUrdAZ0Dic2wJ7DDybbpFAH4HWn1Q uZ2HoerccHyRu9fr04wyQSjTEr3SopH2abYDce3Mm6qz+2wbuKxWiTzfNQFY/ZYxH6 24HX02berlH6j0Tt92PhVHGg0tFPSIW6FBLc0qZM=
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 kTSoigzppgvg; Thu, 15 Oct 2020 21:11:26 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 15 Oct 2020 21:11:26 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 2CC926029B99; Thu, 15 Oct 2020 15:11:25 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 2483E8A8; Thu, 15 Oct 2020 15:11:25 -0400 (EDT)
Date: Thu, 15 Oct 2020 15:11:25 -0400
From: Paul Wouters <paul@nohats.ca>
To: Benno Overeinder <benno@NLnetLabs.nl>
cc: DNSOP Working Group <dnsop@ietf.org>
In-Reply-To: <BF15012C-DB7D-47DB-973F-5745715521E8@NLnetLabs.nl>
Message-ID: <alpine.LRH.2.23.451.2010151506440.2187900@bofh.nohats.ca>
References: <BF15012C-DB7D-47DB-973F-5745715521E8@NLnetLabs.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/4gohuqlc7x4oBhBvjcoW17TonoA>
Subject: Re: [DNSOP] Working Group Last Call for draft-ietf-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: Thu, 15 Oct 2020 19:11:38 -0000

On Thu, 15 Oct 2020, Benno Overeinder wrote:

> This starts a Working Group Last Call for draft-ietf-dnsop-iana-class-type-yang.
>
> Current versions of the draft are available here:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-iana-class-type-yang/

This looks good to me.

One minor item. Is it possible to add text in a way that instructs
implementer they SHOULD NOT add "Obsolete" entries when populating?

Or maybe that could be an instruction to IANA or whoever runs the
"the initial revision" of the yang module?

The idea is that we want to try and stop the proliferation of decades
old stuff into new code/documents just because it has an IANA entry.

Paul

v2.29.0 | Report a Bug | By Email | System Status