Changes between Version 3 and Version 4 of RtgYangArchDT


Ignore:
Timestamp:
19/08/16 17:37:31 (4 years ago)
Author:
lberger@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RtgYangArchDT

    v3 v4  
    11= The Routing Area Yang Architecture design team =
    22
    3 More to come, as it happens...
     3== Version 2: Aug 19, 2016 -> ==
    44
    5 == Charter ==
     5=== Charter ===
     6  [https://mailarchive.ietf.org/arch/msg/rtgwg/RFaWC_ikeBD7zTZd01aVo_ui4Vs Announcement]
     7
     8Going forward, the Design Team will focus on:
     9
     10  *Conventions as specified in the original charter* : Common
     11  conventions and use of YANG functionality in similar ways can
     12  help make the interactions of models easier to understand.  RFC
     13  6087 provides some guidance; an update; is underway now in
     14  draft-ietf-netmod-rfc6087bis.  If the design team has
     15  recommendations for how the models should be written, those
     16  which are not routing-specific can be written down and
     17  discussed in netmod.
     18
     19  *Ideas for how to handle extensions and features as specified in
     20  the original charter*:
     21
     22  It is also important to consider how future extensibility and
     23  features in Routing Area work will need to be captured inYANG
     24  models.  While the IETF is busy developing YANG models, we are
     25  still working on new routing area features and technology.  The
     26  design team should publish and maintain best current practices
     27  for how new features can easily augment existing YANG models so
     28  that authors of those new features and technologies can
     29  understand how to consider YANG modeling.
     30
     31  *Classification*: The ability to specify metadata for
     32  classification and manipulation of models is being defined in
     33  draft-ietf-netmod-yang-mode l-classification-02
     34  <https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/>.
     35  The DT will suggest classifications for Routing Area YANG
     36  models and encourage consistency.
     37
     38  *Support work based on requirements*: The DT will continue to
     39  support work based on requirements from its previous work.  Examples
     40  of such work include draft-ietf-netmod-schema-mount-02
     41  <https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/>
     42  and opstate/revised datastores.
     43
     44  *Progress WG Drafts authored*: The DT and the specific draft
     45  authors will push to publication of the existing drafts:
     46  draft-ietf-rtgwg-device-model-00
     47  <https://datatracker.ietf.org/doc/draft-ietf-rtgwg-device-model/>,
     48  draft-ietf-rtgwg-lne-model-00
     49  <https://datatracker.ietf.org/doc/draft-ietf-rtgwg-lne-model/>,
     50  and draft-ietf-rtgwg-ni-model-00
     51  <https://datatracker.ietf.org/doc/draft-ietf-rtgwg-ni-model/> .
     52
     53  *Consistency of Models across the Routing Area*: The DT will look
     54  at YANG models in the Routing Area and encourage that common
     55  parts be factored out into reusable models.  The DT will look at
     56  how well the set of models will work together and raise any
     57  related issues.  There will be a particular focus on models
     58  expected to progress to RFC in the next 12 months.
     59
     60  *Device Profiles of Needed Models:* Different devices will need
     61  different sets of YANG models for common operations.  There
     62  have been some initial
     63  drafts (e.g. draft-faq-netmod-cpe-yang-profile-00.txt
     64  <https://www.ietf.org/archive/id/draft-faq-netmod-cpe-yang-profile-00.txt>)
     65  in this space.  The DTwill provide guidance for what is needed
     66  in a device profile, as far as the Routing Area aspects, are
     67  concerned and facilitate the creation of appropriate device
     68  profiles.  This should aid in determining what groups of models
     69  are needed for practical use for particular device roles.
     70
     71=== Design team members ===
     72  Acee Lindem <​acee@cisco.com>[[BR]]
     73  Anees Shaikh <​aashaikh@google.com>[[BR]]
     74  Christian Hopps <​chopps@chopps.org>[[BR]]
     75  Dean Bogdanovic <​deanb@juniper.net>[[BR]]
     76  Ebben Aries  <exa@juniper.net>[[BR]]
     77  Lou Berger <​lberger@labn.net>  (lead)[[BR]]
     78  Qin Wu <​bill.wu@huawei.com>[[BR]]
     79  Rob Shakir <​rjs@rob.sh>[[BR]]
     80  Xufeng Liu <xliu@kuatrotech.com>[[BR]]
     81  Yingzhen Qu <yiqu@cisco.com>[[BR]]
     82
     83== Version 1: Mar 26, 2015 -> Aug 19, 2016  ==
     84
     85=== Charter ===
    686[http://www.ietf.org/mail-archive/web/routing-discussion/current/msg02000.html Announcement]
    787
     
    46126  and common conventions, would be published by IETF consensus.
    47127
    48 == Design team members ==
     128=== Design team members ===
    49129  Acee Lindem <acee@cisco.com>[[BR]]
    50130  Anees Shaikh <aashaikh@google.com>[[BR]]