[DNSOP] Robert Wilton's Discuss on draft-ietf-dnsop-iana-class-type-yang-03: (with DISCUSS and COMMENT)

Robert Wilton via Datatracker <noreply@ietf.org> Thu, 03 June 2021 11:16 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F0B173A34AA; Thu, 3 Jun 2021 04:16:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Wilton via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-dnsop-iana-class-type-yang@ietf.org, dnsop-chairs@ietf.org, dnsop@ietf.org, benno@NLnetLabs.nl, benno@NLnetLabs.nl
X-Test-IDTracker: no
X-IETF-IDTracker: 7.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Robert Wilton <rwilton@cisco.com>
Message-ID: <162271898741.9722.1347203006737053876@ietfa.amsl.com>
Date: Thu, 03 Jun 2021 04:16:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/KNTv52phyW4S6-WEgs8YX51LBfQ>
Subject: [DNSOP] Robert Wilton's Discuss on draft-ietf-dnsop-iana-class-type-yang-03: (with DISCUSS and COMMENT)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Jun 2021 11:16:28 -0000

Robert Wilton has entered the following ballot position for
draft-ietf-dnsop-iana-class-type-yang-03: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:



One issue that I think we should should discuss and resolve (sorry for the late
discuss ballot):

In section 4, it states:

   "status":  Include only if a class or type registration has been
      deprecated or obsoleted.  In both cases, use the value "obsolete"
      as the argument of the "status" statement.

I know that we have had some previous discussion on this on Netmod, but, if
draft-ietf-netmod-yang-module-versioning-02 gets standardized then it will
effectively evolve YANG's "status deprecated" into "must implement or
explicitly deviate" and YANG's "status obsolete" into "must not implement".  It
wasn't clear to me that marking one of these fields as being deprecated in an
IANA registry would mean that existing implementations must stop using it if
they migrate to a new version of the generated YANG module.  Hence, I think
that at this stage, it may be safer to map IANA "deprecated" into YANG's
"status deprecated"?



Thanks for this document.  I think that documenting this fields in YANG is a good thing.

One minor nit:

In an couple of places you have used 'analogically' but perhaps meant 'analogously' instead?