[Rtg-yang-coord] Fwd: [Yang-coord] YANG Model Coordination Group directory closure

Alia Atlas <akatlas@gmail.com> Thu, 09 June 2016 16:04 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 (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 3B3C712D85B for <rtg-yang-coord@ietfa.amsl.com>; Thu, 9 Jun 2016 09:04:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Status: No, score=-102.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id pgU8J7TouYqr for <rtg-yang-coord@ietfa.amsl.com>; Thu, 9 Jun 2016 09:04:27 -0700 (PDT)
Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE99B12D84C for <Rtg-yang-coord@ietf.org>; Thu, 9 Jun 2016 09:04:26 -0700 (PDT)
Received: by mail-qg0-x232.google.com with SMTP id q32so22681366qgq.3 for <Rtg-yang-coord@ietf.org>; Thu, 09 Jun 2016 09:04:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=J8iubSpKSnqaJ3NCjD/LE8mcYjdcVddcjAKC/+XoPNE=; b=IagVwFlycZruZHfhaRxR5NeDXCIrfyt2SyxCCKgFARsO3sviecAEEWmZ9LMJynuUGx 6hPkPWHu+Es0Ay+9vv7fxRwIVmTb+qWMkyAHhcSXcx9YVEMye31RmEWMZkb8T3oHBMGL uD75QnV5F72MYwT5aTzI8FbTeKxZLEyiJJs1pvdO1vBgd6WXCeG1mfyhLMjf58DIGtto 5TDI6PwrUIMVLwLXVTMbNwNkicE19z3jSz43wqygg5rLhrDJAFJ4T7BQKTiLjqXnDWkk GkK9cYBLSjrh/RyXPmy1nlq4Dd0BX6dTtkMXWpkJrIKM1W5p+Fqk7vUPgXA+YMo8xhzC BcSQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=J8iubSpKSnqaJ3NCjD/LE8mcYjdcVddcjAKC/+XoPNE=; b=jtuO6kRwgM/+QObYmEKS5XrIs3V0E9JVLKuMV0tNwpEY211pgWlgefFxSbu7JeVsNY HaVFxU+70raSe4S0p5s/WFkoTx+Acd6Zxhs5gAlrJFfP2T3sKDEK3p8jvLcP1ImQkiib 6xct8sXXFHRHxDd/Jo8wa15/iuHtQbyS5pAWLrFEsl074fY+6VHL2wwWRT2+6zAYmpHg z1o0vbjS7YgqtC5Vl7aOh2OkugVAsmQESr73lw+BQUr8SpH5/RB5jgs05hBsTSXUutcB GAJREtGHwN/IJL1rigyCqoQfEx8MFYq6KtgvjUR+Jd3k68IBeItcV7tZ7LuijS2efTpH 8iMA==
X-Gm-Message-State: ALyK8tItbAUkmiM//vtLD8vLywP8e8TvRl/jggRwfdM2Ly3hX2dHWTDNrQ4bEEQPQ/feIhSGKbCHcgb05H0m0A==
X-Received: by with SMTP id y2mr3660217qhc.68.1465488265834; Thu, 09 Jun 2016 09:04:25 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Thu, 9 Jun 2016 09:04:25 -0700 (PDT)
In-Reply-To: <daeacfea-b133-3519-f64f-0e02e231ce3e@cisco.com>
References: <f6e96e9a-efc7-345d-205b-e7d1d2b0c021@cisco.com> <daeacfea-b133-3519-f64f-0e02e231ce3e@cisco.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Thu, 9 Jun 2016 12:04:25 -0400
Message-ID: <CAG4d1rf-RP-sEcLBUK9yCF3801yPXqogmFBWSXnddcoBk_wFMw@mail.gmail.com>
To: "Rtg-yang-coord@ietf.org" <Rtg-yang-coord@ietf.org>
Content-Type: multipart/alternative; boundary=001a113aa918820e8e0534da93bf
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-yang-coord/Vq24_GuAkkZHoMLiSreLAV0yHIE>
Subject: [Rtg-yang-coord] Fwd: [Yang-coord] YANG Model Coordination Group directory closure
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 09 Jun 2016 16:04:29 -0000


---------- Forwarded message ----------
From: Benoit Claise <bclaise@cisco.com>
Date: Thu, Jun 9, 2016 at 11:35 AM
Subject: [Yang-coord] YANG Model Coordination Group directory closure
To: IETF-Discussion list <ietf@ietf.org>rg>, "yang-coord@ietf.org" <

Dear all,

The YANG Model Coordination Group
has been a success, and has served its purpose.

The plan and the time commitment (each person committed to spend 1/3 of his
time) for this group were ambitious:

   - Phase 1: List of the YANG models (inventory)
   - Phase 2: Tooling
   - Phase 3: Help with compilation
   - Phase 4: Training & Education
   - Phase 5: Coordination across SDOs/Opensource
   - Phase 6: Model Coordination within the IETF
   - Phase 7: Standardization Priorities

Let's review the achievements. Quiet impressive for a couple of volunteers
if you ask me.

Phase 1: List of the YANG models (inventory)
    Extracted all YANG data models from IETF drafts and RFCs on
    Started to work on YANG data model catalog for the industry

Phase 2: Tooling
    YANG data models extraction from drafts/RFCs
    YANG data models dependency visualization
    YANG data model grouping extraction and compilation
    Created http://www.yangvalidator.org/
    pyang integration in idnits/tracker
    pyang plugin for the YANG data model catalog
    Along the process we filed a couple of pyang bugs
    Organized the YANG track at the IETF Hackathon

Phase 3: Help with compilation
    Proactively contacted the IETF draft authors, discussing their compilation
error messages <http://www.claise.be/IETFYANGPageCompilation.html>
    Kept track of the situation here
    Flagged the duplicate YANG module names, groupings, etc.

Phase 4: Training & Education
    Created some training materials, presented at IETF94
    NETCONF Slides
YANG Slides
pyang Slides <https://datatracker.ietf.org/doc/slides-edu-pyang-tutorial/>

Phase 5: Coordination across SDOs/Opensource
    Coordinated with the IEEE/MEF/BBF, amongst others
    Worked on the YANG Data Model Classification,
accepted as NETMOD WG document
    Based on github, we're compiling the IEEE/BBF/Opendaylight/openconfig
data models <http://www.claise.be/YANGPageMain.html>
    Helped on URN for different SDOs
    YANG Modeling Efforts in the Industry

Phase 6: Model Coordination within the IETF
    We helped with the coordination, even if the YANG routing design team
    contributed significantly for the routing aspects.

Phase 7: Standardization Priorities
    This is maybe where we haven't had enough time to dedicate,
    even if we have identified the next steps.
    See YANG Data Models in the Industry: Current State of Affairs

I probably missed some of the achievements. Sorry about that.

Let's analyze the current situation!
It's difficult, in a voluntary-based organization to dedicate so much time
on this YANG effort. On the other hand, this group efforts helped with the
heavy-lifting job to promote YANG in the industry. Thanks for that. These
days, even if it doesn't translate yet in many RFC numbers, YANG became a
mature technology, which can now rely on a bigger community.
I expect that the YANG doctors
<https://www.ietf.org/iesg/directorate/yang-doctors.html> to take over some
of the effort here, helping with the proactive review of YANG data models.
More on this later.
Regarding the tooling aspects, the IETF hackathon will continue to play an
important role: a couple of people signed up already

Thanks to Carl, Dean, and Qin as YANG Model Coordination Group members, and
to many others who helped directly or indirectly.

I will now request to close this directorate.

Regards, Benoit (OPS AD)

Yang-coord mailing list