From nobody Fri Aug 19 10:08:24 2016 Return-Path: X-Original-To: rtg-yang-coord@ietfa.amsl.com Delivered-To: rtg-yang-coord@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 Date: Fri, 19 Aug 2016 13:07:54 -0400 Message-ID: To: "routing-discussion@ietf.org" , "Rtg-yang-coord@ietf.org" , "rtgwg@ietf.org" Content-Type: multipart/alternative; boundary=94eb2c1244b64d10cc053a6fbd96 Archived-At: Subject: [Rtg-yang-coord] Reorganizing & updating the Routing Yang Architecture Design Team 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\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Aug 2016 17:08:02 -0000 --94eb2c1244b64d10cc053a6fbd96 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable In March 2015, I created the Routing Yang Architecture Design Team and specified a charter . 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 , draft-ietf-rtgwg-lne-model-00 , and draft-ietf-rtgwg-ni-model-00 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 mod= els 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 . 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 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-0= 0 , draft-ietf-rtgwg-lne-model-00 , and draft-ietf-rtgwg-ni-model-00 . *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 ) 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 <=E2=80=8Blberger@labn.net> (lead) Acee Lindem <=E2=80=8Bacee@cisco.com> Christian Hopps <=E2=80=8Bchopps@chopps.org> Dean Bogdanovic <=E2=80=8Bdeanb@juniper.net> Rob Shakir <=E2=80=8Brjs@rob.sh> Anees Shaikh <=E2=80=8Baashaikh@google.com> Qin Wu <=E2=80=8Bbill.wu@huawei.com> Ebben Aries Yingzhen Qu Xufeng Liu I would like to thank Yan Gang and Stephane Litkowski for their willingness to help and efforts over the last 17 months. Regards, Alia --94eb2c1244b64d10cc053a6fbd96 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
The Design Team has done some excellent work helping to = steer and define the work being done.=C2=A0 This includes=C2=A0draft-ietf-rtgwg-device-model-00,=C2=A0draf= t-ietf-rtgwg-lne-model-00, and=C2=A0draft-ietf-rtgw= g-ni-model-00=C2=A0as well as identifying issues and work needed t= o be done in NetMod around improving=C2=A0YANG, such as schema= mount and opstate/revised datastores.

At this point, 17 months in, it = is time to reorganize the=C2=A0DT=C2=A0a bit, set additional g= oals, 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=C2=A0:=C2=A0Common = conventions and use of=C2=A0YANG=C2=A0=C2=A0 functionality in = similar ways can help make the interactions of models easier to understand.= =C2=A0 RFC 6087 provides some guidance; an update is underway now in draft-= ietf-netmod-rfc6087bis.=C2=A0 If the design team has recommendations for ho= w 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:=C2=A0
It is also importa= nt to consider how future extensibility and features in Routing Area work w= ill need to be captured inYANG=C2=A0models.=C2=A0 While the IE= TF is busy developing=C2=A0YANG=C2=A0models, we are still work= ing on new routing area features and technology.=C2=A0 The design team shou= ld publish and maintain best current practices for how new features can eas= ily augment existing=C2=A0YANG=C2=A0models so that authors of = those new features and technologies can understand how to consider=C2=A0YANG=C2=A0modeling.

Classification: =C2=A0The abili= ty to specify metadata for classification and manipulation of models is bei= ng defined in=C2=A0draft-ietf-netmod-yang-model-classification-02.=C2=A0 The=C2=A0DT=C2=A0will suggest classifications for Routing Area=C2=A0YANG=C2=A0models and encourage consistency.

Support work based on re= quirements: =C2=A0The=C2=A0DT=C2=A0will continue to suppor= t work based on requirements from its previous work.=C2=A0 Examples of such= work include=C2=A0
draft-ietf-netmod-schema-mount-02=C2=A0and opstate/revised datastores.

Progress WG Draft= s authored: =C2=A0The=C2=A0DT=C2=A0and the specific draft = authors will push to publication of the existing drafts:=C2=A0draft-ietf-rtgwg-device-model-00,=C2=A0draft= -ietf-rtgwg-lne-model-00, and=C2=A0draft-ietf-rtgwg= -ni-model-00=C2=A0.

Consistency of Models across the Rou= ting Area: =C2=A0The=C2=A0DT=C2=A0will look at=C2=A0= YANG=C2=A0models in the Routing Area and encourage that common parts= be factored out into reusable models.=C2=A0 The=C2=A0DT=C2=A0= will look at how well the set of models will work together and raise any re= lated issues.=C2=A0 There will be a particular focus on models expected to = progress to RFC in the next 12 months.

Device Profiles of Needed = Models:=C2=A0 Different devices will need different sets of=C2=A0= YANG=C2=A0models for common operations.=C2=A0 There have been some i= nitial drafts (e.g.=C2=A0draft-faq-netmod-cpe-<= span>yang-profile-00.txt) in this space.=C2=A0 The=C2=A0DTwill provide guidance for what is needed in a device profile, a= s far as the Routing Area aspects, are concerned and facilitate the creatio= n of appropriate device profiles.=C2=A0 This should aid in determining what= groups of models are needed for practical use for particular device roles.=

The Design Team membe= rs will include:

Lou Berger <<= a href=3D"mailto:lberger@labn.net" style=3D"color:rgb(68,0,136);border-bott= om-width:0px;font-family:"Times New Roman",times,serif;font-size:= 14.6667px" target=3D"_blank">=E2=80=8Blberger@labn.net> =C2=A0(lead)
Christian = Hopps <=E2=80=8Bchopps@chopps.org&= gt;
Dean Bogdanovic <=E2=80=8Bdeanb@juniper.net>
Rob Shakir <=E2=80=8Brjs@rob.sh>
=
Ebben Aries =C2=A0<exa@juniper.net>
Yingzhen Qu <yiqu@cisco.com>
Xufeng Liu=C2=A0<xliu@kuatrotech.com>

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

Regards,=
Alia
--94eb2c1244b64d10cc053a6fbd96--