[Rtg-yang-coord] AD statement on development of IETF-standard routing-related YANG models
Alia Atlas <akatlas@gmail.com> Wed, 29 October 2014 13:57 UTC
Return-Path: <akatlas@gmail.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C8621A00F9; Wed, 29 Oct 2014 06:57:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 TLF1Imw1hg1J; Wed, 29 Oct 2014 06:57:29 -0700 (PDT)
Received: from mail-yh0-x236.google.com (mail-yh0-x236.google.com [IPv6:2607:f8b0:4002:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 932891A00C5; Wed, 29 Oct 2014 06:57:29 -0700 (PDT)
Received: by mail-yh0-f54.google.com with SMTP id 29so620250yhl.41 for <multiple recipients>; Wed, 29 Oct 2014 06:57:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=BwnTZECvvNx90SFa8DAr6GYoKbKePaGi2Tljee1FNSE=; b=ejPcU02K3h6nXB75q5f0yt4+l9WuY24COqQpk/HxuH4LcBHCSVPQjD+Nhzo8/1eR2G lMy4cbMZGcdtU1HPv2txhW/i+T8Qrk5WgjOSLD8AUtdOWbuv6FyRStSjW26LNMxY1IbL BrVSrrQQpelvyDgZsjeDg2i7cjBNbW+/7uMOcREY+vPmLQ1tln6OQSKtSijodumUgqm8 72X897EvA00A5AdWqsJW3uFx5XEx1gRkefJTVHmSXMmrGO5MnPwQ/VmG86kWNepTwuLp YDJpicN/ytw+RUX6hbuaKT0RhckTWhqqfOi6PODgcXhnauvPQb4QVwl564tXEmQQJdmS qyDA==
MIME-Version: 1.0
X-Received: by 10.236.23.231 with SMTP id v67mr1925171yhv.48.1414591048880; Wed, 29 Oct 2014 06:57:28 -0700 (PDT)
Received: by 10.170.113.10 with HTTP; Wed, 29 Oct 2014 06:57:28 -0700 (PDT)
Date: Wed, 29 Oct 2014 09:57:28 -0400
Message-ID: <CAG4d1rfrKwh0MtvdOoLz9rhSDUQNsYv7n_Do1-zwo7Ln3suHSQ@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: "netmod@ietf.org" <netmod@ietf.org>, "Rtg-yang-coord@ietf.org" <Rtg-yang-coord@ietf.org>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Content-Type: multipart/alternative; boundary="089e0122a6caf8966a05069024f8"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/f7XLc9U3q32QLcat9p3OLhJrkSg
Subject: [Rtg-yang-coord] AD statement on development of IETF-standard routing-related YANG models
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Oct 2014 13:57:33 -0000
Development of standardized YANG models has seriously increased this year. Of course, this is a good problem to have. There are close to 30 different drafts related to YANG models for routing; coordination between these drafts is necessary. NETMOD is also hard at work on a backwards-compatible YANG 1.1. From the IETF's experience with developing MIBs, it was critical to have the domain-area experts involved in writing and reviewing MIBs and we believe that it is similarly critical to situate the work on YANG models in the working groups where the appropriate domain-experts can be easily found. Actively encouraging and cultivating the review of those with the expertise in modeling with YANG and deep understanding of its features is also critical to the success of standardized YANG models. This expertise is found in the NETMOD working group and among the YANG doctors ( https://www.ietf.org/iesg/directorate/yang-doctors.html). We, as the Routing and Ops and Management Area Directors, would like to see work proceed as follows. 1) The mailing list, rtg-yang-coord@ietf.org, has been created to coordinate among the different routing YANG models and drafts. For instance, there may be common groupings to be defined, interactions between models to be determined, and so on. To facilitate this coordination work, we are developing a job description for a secretary for the mailing list and hope to appoint someone to that role. 2) Routing-related YANG models must be targeted for adoption at the appropriate WGs in the Routing Area. If the appropriate WG is unclear, please bring the question to the RTGWG and the rtg-yang-coord@ietf.org mailing list. RTGWG can either direct where the work goes or, if there is no appropriate other WG, make a decision about adopting the draft. 3) The NETMOD charter has been open to accept work item that don't fall under the responsibility of an existing WGs: The NETMOD WG may also develop any additional data models written in YANG that the WG considers core building blocks and that do not fall under the charters of other active IETF working groups. The NETMOD WG may simply add such milestones as it sees fit, with the advice and consent of the responsible AD. In case of routing-related YANG models, even if there are no responsible existing WG, it's expected that the standardization happens in the RTGWG. 4) It is common and expected that sometimes work needs to be discussed in multiple WGs, even though it is only adopted in one. Examples would include NETMOD discussing a model for OSPF to consider how it relates to draft-ietf-netmod-routing-cfg, RTGWG discussing draft-ietf-netmod-routing-cfg to encourage review and discussion about its use as a base for routing-related models, etc. 5) We have heard a strong desire from the community to rapidly encourage development of standardized YANG models. Towards that end, we expect and encourage more and frequent virtual interims (some probably joint between WGs). To have such a pace work well, we need authors, reviewers, and contributors to expect to spend time on this work on an on-going basis. 6) Since many YANG doctors also participate in NETMOD and since NETMOD is having weekly virtual interims, it may prove convenient to provide feedback on YANG models in this forum. When done so, to ensure the interested parties are aware of the relevant models to be discussed and can arrange their schedules to call in, the agenda should be forwarded with at least a week's to the rtg-yang-coord@ietf.org and to the relevant WGs. When the virtual interim is used to provide YANG doctor feedback, preference should be given to drafts already adopted by a WG; discussing one model does not imply partiality or a request to the WG appropriate to consider adopting the draft. 7) To provide a common location to find proposed YANG models and be able to verify their accuracy, Tom Nadeau, one of the NETMOD chairs, has set up a GitHub repository at: https://github.com/YangModels/yang. All work contributed to it is subject to the IETF Contributions policy, as summarized via the very very familiar IETF Note Well. 8) For the second IETF meeting in a row, a "YANG Advice and Editing Session" (http://www.ietf.org/meeting/91/tutorials/yang-session.html) is organized on the Sunday before the IETF meeting. This is your chance to sit down with a YANG doctor and to get feedback on your YANG module. If you have any questions, please let us know. Regards, Alia, Benoit, Adrian, & Joel