Re: [netmod] Important: Guidelines for YANG module authors

Andy Bierman <> Fri, 09 June 2017 17:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5120A127010 for <>; Fri, 9 Jun 2017 10:06:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id mHOlxlPOXM-M for <>; Fri, 9 Jun 2017 10:06:27 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:400c:c0c::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DB6331270A3 for <>; Fri, 9 Jun 2017 10:06:26 -0700 (PDT)
Received: by with SMTP id v111so39669778wrc.3 for <>; Fri, 09 Jun 2017 10:06:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IJ2qyjEzGrCUR0+QBWc6PVxF9nWe6jaq820IAbVc4w8=; b=alNxKlzg9zBxC3/G7xMClS64svkyXUtFPXrPVh8rttzoSvn8hO7/Kdj+MUIQMygTZ9 m7XzpluHddRhgGExRuUXPOTSe7lVLGhRtyW7eroDh31fkOjID/h41M3Osvz9SHlfPmDk GkPj8ogsoTc+7KUNFFvLvLcMDnZz81uHJyOlg+pNsq+qMe1K6q6o4SfncvTmgNo8IGZV jFmzlV8oYmAfFtFM3rDzfH3lQ5V2N6mk2dBVxHaUvZ5HueJv8oasHvxzyE0T7AiJS7wZ SsiABoT4YiE7T6jZECxy+jc8oLSdt41TExHgvcBw7sHsdg2dp2YDu4aw+W4gqm5ZxoAR aaQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IJ2qyjEzGrCUR0+QBWc6PVxF9nWe6jaq820IAbVc4w8=; b=EMnu1xDsbHbPkCYKeu/7ur/Ppt1wMDJBeOgxHlbAaYtL8ujDUxZNp1gxbuiujCV9Te FqXneVCEoGNYhTjKZvcpIg1GiD6cCHqEN1IGGSaEWPvewQd2HVdS7G89IzNEw/nptu4p iPff9wbmQC9ePoqiJhXLjPldw/WBCd06Uc2qytjB0XyVXLOBlaeCCutneOm2gSIfY7/y KcYDQ20+PqJh9KetOEDvrFN9dRY1hvFoeXND5AlpjCnM9mQ302fS11ns2B7b6rJuluuU EdHzdh2yihySb/P/u/BuQwyRUKbodKSVVGkKSDm5U4u7k+F2UC66Bn2wAHyV2uJErYef 8aiA==
X-Gm-Message-State: AKS2vOymhwsa7dJMhc4qT8Brbe7g2VcDZjqNgt6pWz0XxQLDI2JtIuNt 6OdXqKblYdfUs9rR9i/V1DBsPFze+GpD
X-Received: by with SMTP id e192mr585847wmf.48.1497027985411; Fri, 09 Jun 2017 10:06:25 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Fri, 9 Jun 2017 10:06:24 -0700 (PDT)
In-Reply-To: <>
References: <>
From: Andy Bierman <>
Date: Fri, 9 Jun 2017 10:06:24 -0700
Message-ID: <>
To: Benoit Claise <>
Cc: NETMOD Working Group <>
Content-Type: multipart/alternative; boundary="f403045f55e24a2196055189fd7d"
Archived-At: <>
Subject: Re: [netmod] Important: Guidelines for YANG module authors
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 09 Jun 2017 17:06:30 -0000


I am trying to complete rfc6087bis.
It has been held up waiting for this draft.
It is not clear to me how sec. 6.23 (Operational Data) needs to change.
Should the whole section be replaced by an informative reference to this
new draft?


On Fri, Jun 9, 2017 at 6:56 AM, Benoit Claise <> wrote:

> Dear all,
> Now that the new NETMOD and NETCONF charters have been approved, it's time
> to think about the guidelines for YANG module authors.
> The Network Management Datastore Architecture (NMDA) addresses the
> so-called "OpState problem" that has been the subject of much discussion in
> the IETF. NMDA is still in development, and there will be a transition
> period before NMDA solutions are universally available.
> The NETMOD Datastore Design Team and the Routing Yang Architecture Design
> Team have worked with Alia and Benoit to create initial guidelines for how
> the NMDA, as defined in draft-ietf-netmod-revised-datastores
> <>,
> impacts Yang models. The draft-dsdt-nmda-guidelines
> <> individual
> draft was foundational in helping creating those guidelines.
> If you have questions or concerns on how these guidelines should apply to
> work of interest, please contact your WG Chairs or ADs.
> It is our strong recommendation, as ADs with agreement from the NETMOD WG
> Chairs, that models SHOULD move as quickly as possible to the NMDA. The
> specific approach to be taken for models being developed now and during the
> NMDA transition period should be based on both the expected usage and the
> maturity of the data model.
> 1. New models and models that are not concerned with the operational state
> of configuration information SHOULD immediately be structured to be
> NMDA-compatible.
> 2. Models that require immediate support for "in use" and "system created"
> information SHOULD be structured for NMDA. Then derived versions of these
> models SHOULD be created, either by hand or with suitable tools, that
> follow the current modeling strategies. In some cases, the non-NMDA model
> may be an existing model and not derived from the NMDA model. In all cases,
> the NMDA and non-NMDA modules SHOULD be published in the same document,
> with NMDA modules in the document main body and the non-NMDA modules in an
> Appendix. The use of the non-NMDA model will allow temporary bridging of
> the time period until NMDA implementations are available. The non-NMDA
> module names should include ’-state’ appended.
> We would like to thank Kent Watsen, Lou Berger, Rob Wilton, Martin
> Bjorklund, Phil Shafer, Acee Lindem, Chris Hopps, Juergen Schoenwaelder,
> and all others who helped develop these guidelines.
> Regards,
> Alia Atlas, Routing AD
> Deborah Brungard, Routing AD
> Alvaro Retana, Routing AD
> Warren Kumari, Operations & Management AD
> Benoit Claise, Operations & Management AD
> _______________________________________________
> netmod mailing list