Reorganizing & updating the Routing Yang Architecture Design Team

Alia Atlas <akatlas@gmail.com> Fri, 19 August 2016 17:08 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F0F812D5F0; Fri, 19 Aug 2016 10:08:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.906
X-Spam-Level:
X-Spam-Status: No, score=-101.906 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, HTML_OBFUSCATE_10_20=0.093, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 PyFMxBSp3LxU; Fri, 19 Aug 2016 10:07:59 -0700 (PDT)
Received: from mail-ua0-x230.google.com (mail-ua0-x230.google.com [IPv6:2607:f8b0:400c:c08::230]) (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 6CD6A12D586; Fri, 19 Aug 2016 10:07:56 -0700 (PDT)
Received: by mail-ua0-x230.google.com with SMTP id 97so90403618uav.3; Fri, 19 Aug 2016 10:07:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=PtlG4VgU6xZmk801MbQ/nVodK1DseZKWugF2pOKP85k=; b=mJbLNdpAwcMNvGFyoSpSkChEPZwd10DDA3ZDKYzA/MYzENmcOQfR67TRGo9uIXhKCf Xarq9TSL7et4FE0qbOY2JVzsPghXeUpRbtN56FKx/pRjfMdgiB12Vs6MJlJoUE9ABu0U 5AUXq0arh4V5x2r9B3bZCYeLVZDFqqomzW4en0d2iStJSDVaDz3E4YvAmpKzQbk0WSq+ 0Y9KoAwyf1GfV2TB7moRJimfRTkOFOl9M5K+v3FqB+l9pT4dOZUXVdiQ+1IvGt0wgM/P uPQVtKiaC1fYVXGZeGrRDnO3FZya1es/mekf1VLI5DbEyMS1xrXJUb/U4JiA8yCJC99B jHeA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=PtlG4VgU6xZmk801MbQ/nVodK1DseZKWugF2pOKP85k=; b=czdVvD/CSzWYu73DPs5QAMlrNcN5TxCaLewLIvN5TA38Z0uMC7+HxUWFwyTxzNcGY3 nElu+7y2ApA3pW7t5950siqlqhIWOfWs4RSsPmBFohvmIn06x2dxN6gsPUTA1IbP9wJe HRN3HQmf8sW+vGhqgdZnMFnU+P3BNhYwws9F4/l4K88NMTrazY/8SQEJCwTbqyKNsiw8 QTjIJP1+yFd8hN9THu7r0UhbiDyZ1riqw1pHHVhYToR4GVcqGbsucFZH8dBjTpVBBoBJ pXBu85rQD3pdkvwI5bUeUhdTDbtu5P9tjXqraT3BFhqmMKVQpZC9NiRAz6vZYJ//UPw+ EE/g==
X-Gm-Message-State: AEkooutfMZYWgKDX3TAFBWOQHdLvmgiBr4vkdj4tJ05TSqmVnKvxXRaYcfdZtIsCtLZ2rZW9HL/f5SRpogRFjw==
X-Received: by 10.159.39.228 with SMTP id b91mr4799082uab.41.1471626475276; Fri, 19 Aug 2016 10:07:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.50.7 with HTTP; Fri, 19 Aug 2016 10:07:54 -0700 (PDT)
From: Alia Atlas <akatlas@gmail.com>
Date: Fri, 19 Aug 2016 13:07:54 -0400
Message-ID: <CAG4d1restkyqtSHPeApNkVj18ARbsszmMRHxBnjUeV3L3bWe0A@mail.gmail.com>
Subject: Reorganizing & updating the Routing Yang Architecture Design Team
To: "routing-discussion@ietf.org" <routing-discussion@ietf.org>, "Rtg-yang-coord@ietf.org" <Rtg-yang-coord@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c1244b64d10cc053a6fbd96
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/RFaWC_ikeBD7zTZd01aVo_ui4Vs>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2016 17:08:02 -0000

In March 2015, I created the Routing Yang Architecture Design Team and
specified a charter
<https://www.ietf.org/mail-archive/web/routing-discussion/current/msg02000.html>
.
The Design Team has done some excellent work helping to steer and define
the work being done.  This includes draft-ietf-rtgwg-device-model-00
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-device-model/>;,
draft-ietf-rtgwg-lne-model-00
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-lne-model/>;, and
draft-ietf-rtgwg-ni-model-00
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-ni-model/> as well as
identifying issues and work needed to be done in NetMod around improving
YANG, such as schema mount and opstate/revised datastores.

At this point, 17 months in, it is time to reorganize the DT a bit, set
additional goals, say thank you to some members and add some others who are
interested.

Going forward, the Design Team will focus on:

*Conventions as specified in the original charter* : Common conventions and
use of YANG   functionality in similar ways can help make the interactions
of models easier to understand.  RFC 6087 provides some guidance; an update
is underway now in draft-ietf-netmod-rfc6087bis.  If the design team has
recommendations for how the models should be written, those which are not
routing-specific can be written down and discussed in netmod.

*Ideas for how to handle extensions and features as specified in the
original charter*:

It is also important to consider how future extensibility and features in
Routing Area work will need to be captured inYANG models.  While the IETF
is busy developing YANG models, we are still working on new routing area
features and technology.  The design team should publish and maintain best
current practices for how new features can easily augment existing YANG models
so that authors of those new features and technologies can understand how
to consider YANG modeling.

*Classification*:  The ability to specify metadata for classification and
manipulation of models is being defined in draft-ietf-netmod-yang-mode
l-classification-02
<https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/>;.
The DT will suggest classifications for Routing Area YANG models and
encourage consistency.

*Support work based on requirements*:  The DT will continue to support work
based on requirements from its previous work.  Examples of such work
include
draft-ietf-netmod-schema-mount-02
<https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/> and
opstate/revised datastores.

*Progress WG Drafts authored*:  The DT and the specific draft authors will
push to publication of the existing drafts: draft-ietf-rtgwg-device-model-00
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-device-model/>;,
draft-ietf-rtgwg-lne-model-00
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-lne-model/>;, and
draft-ietf-rtgwg-ni-model-00
<https://datatracker.ietf.org/doc/draft-ietf-rtgwg-ni-model/> .

*Consistency of Models across the Routing Area*:  The DT will look at
YANG models
in the Routing Area and encourage that common parts be factored out into
reusable models.  The DT will look at how well the set of models will work
together and raise any related issues.  There will be a particular focus on
models expected to progress to RFC in the next 12 months.

*Device Profiles of Needed Models:*  Different devices will need different
sets of YANG models for common operations.  There have been some initial
drafts (e.g. draft-faq-netmod-cpe-yang-profile-00.txt
<https://www.ietf.org/archive/id/draft-faq-netmod-cpe-yang-profile-00.txt>)
in this space.  The DTwill provide guidance for what is needed in a device
profile, as far as the Routing Area aspects, are concerned and facilitate
the creation of appropriate device profiles.  This should aid in
determining what groups of models are needed for practical use for
particular device roles.

The Design Team members will include:

Lou Berger <​lberger@labn.net>;  (lead)
Acee Lindem <​acee@cisco.com>;
Christian Hopps <​chopps@chopps.org>;
Dean Bogdanovic <​deanb@juniper.net>;
Rob Shakir <​rjs@rob.sh>;
Anees Shaikh <​aashaikh@google.com>;
Qin Wu <​bill.wu@huawei.com>;
Ebben Aries  <exa@juniper.net>;
Yingzhen Qu <yiqu@cisco.com>;
Xufeng Liu <xliu@kuatrotech.com>;

I would like to thank Yan Gang and Stephane Litkowski for their willingness
to help and efforts over the last 17 months.

Regards,
Alia