Re: [netmod] draft netmod charter update proposal

Kent Watsen <kwatsen@juniper.net> Fri, 03 March 2017 15:23 UTC

Return-Path: <kwatsen@juniper.net>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A057E129458; Fri, 3 Mar 2017 07:23:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.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 s-7VjyjRf6mP; Fri, 3 Mar 2017 07:23:23 -0800 (PST)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0123.outbound.protection.outlook.com [104.47.36.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB3581298AE; Fri, 3 Mar 2017 07:23:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=kF4J92XbKcLHdNyau0WAOO2KeNSOx8Ag0UsM4tlwwew=; b=WY7v32aL8aALailL8nxsYEiKtXKQZMc+5kERY5tDy9ua0129cSjquqO4az8UervNWcmgAk3CH6G3D+l/jCafjKUfNnO/5QqI+S7MTfb78jrwAvfSHe0dgjGa7shHpiJ8OXPu6UQ5qohar0lz9oEXEZKaztXRdILJmwoTLecOTMg=
Received: from BN3PR0501MB1442.namprd05.prod.outlook.com (10.160.117.151) by BN3PR0501MB1441.namprd05.prod.outlook.com (10.160.117.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.2; Fri, 3 Mar 2017 15:23:21 +0000
Received: from BN3PR0501MB1442.namprd05.prod.outlook.com ([10.160.117.151]) by BN3PR0501MB1442.namprd05.prod.outlook.com ([10.160.117.151]) with mapi id 15.01.0947.015; Fri, 3 Mar 2017 15:23:21 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] draft netmod charter update proposal
Thread-Index: AQHSjWtMgvd1I9y/IUSjVG5c54oSBqF9KfeA///YNICAAaCFAIAAJwsAgAQrygA=
Date: Fri, 3 Mar 2017 15:23:21 +0000
Message-ID: <030A7AF8-BA6E-4622-B008-F9624012C972@juniper.net>
References: <B6359563-0649-453A-B29F-28375F2BD3A4@juniper.net> <0830e87c-ee4f-bf53-2c51-96c166d3955e@cisco.com> <9A9AD440-953D-46D4-9207-97619D054912@juniper.net> <9d7b60aa-1690-c598-7034-2e430c7a8e0a@cisco.com> <3C31A53A-6818-451E-9BEF-5E568C4DCB65@juniper.net>
In-Reply-To: <3C31A53A-6818-451E-9BEF-5E568C4DCB65@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1f.0.170216
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=juniper.net;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [66.129.241.11]
x-ms-office365-filtering-correlation-id: e8f5a021-3786-45ff-72c1-08d462493a47
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:BN3PR0501MB1441;
x-microsoft-exchange-diagnostics: 1; BN3PR0501MB1441; 7:aIJGtMqC8tO+4i6wlVM7KAz/ibC6iRr4tGNOA+TYLRSJ+0DXSuyRc6doc9YIpGd3xJ9mrqRDSuxiyf8Nw5VewlcPeMrAWuamTvrWaPo5uRZrfwArsLK/Zjr0dP4UBZ2vu1EugAAz4/AvfopQpJj/66N22bUgqJlBLP/9D/bgQZtp5HlhtVXwWngbdPAOlzC0kfgo7PbOr6+husBsKK47eoFkzibqIVyh3akDB1Tkr1tNe9m58a9coCY+tL2+gseNNXP9T0uepiYTLiDuYLpYYdsc2v47ZMkbKjw1Uzc4vYRA+9YclsBOhw2oCQX+ZbtnfytMYQbxGI2h55Bzn2E6Fg==
x-microsoft-antispam-prvs: <BN3PR0501MB144144AFBB3C7D76FC945FE1A52B0@BN3PR0501MB1441.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(35073007944872)(138986009662008)(95692535739014)(50582790962513);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(6041248)(20161123562025)(20161123564025)(20161123560025)(20161123555025)(20161123558025)(6072148); SRVR:BN3PR0501MB1441; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0501MB1441;
x-forefront-prvs: 0235CBE7D0
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(39860400002)(39850400002)(39840400002)(39450400003)(39410400002)(45074003)(229853002)(6116002)(8676002)(102836003)(66066001)(53936002)(1730700003)(3280700002)(38730400002)(3846002)(122556002)(110136004)(450100001)(8936002)(81166006)(6246003)(2906002)(189998001)(92566002)(3660700001)(5660300001)(33656002)(15650500001)(6512007)(36756003)(4001350100001)(2501003)(93886004)(4326008)(106116001)(2351001)(6436002)(2950100002)(6916009)(83716003)(6486002)(77096006)(5640700003)(305945005)(6506006)(99286003)(6306002)(2900100001)(7736002)(50986999)(25786008)(83506001)(82746002)(86362001)(54356999)(76176999)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0501MB1441; H:BN3PR0501MB1442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <F96325D253EDF346958E46F002D74E2E@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Mar 2017 15:23:21.5196 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0501MB1441
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/EFTf4Ffv3vCk3aX1gCRDZcd2wdg>
Cc: "netmod-chairs@ietf.org" <netmod-chairs@ietf.org>
Subject: Re: [netmod] draft netmod charter update proposal
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Mar 2017 15:23:37 -0000

Hi NETMOD WG,

Please find below draft-3 having the following changes:

 - s/representation/encoding/g
 - s/2016/2017/ in Milestones
 - moved syslog from Mar to Apr
 - moved entity from Mar to Apr

Any other comments?

Kent




Network Modeling (NETMOD)  
-------------------------

Charter

Current Status: Active

Chairs:
   Lou Berger <lberger@labn.net>
   Kent Watsen <kwatsen@juniper.net>

Operations and Management Area Directors:
   Benoit Claise <bclaise@cisco.com>
   Joel Jaeggli <joelja@bogus.com>

Operations and Management Area Advisor:
   Benoit Claise <bclaise@cisco.com>

Secretary:
   Zitao (Michael) Wang <wangzitao@huawei.com>

Mailing Lists:
   General Discussion: netmod@ietf.org
   To Subscribe:       https://www.ietf.org/mailman/listinfo/netmod
   Archive:            https://mailarchive.ietf.org/arch/browse/netmod/

Description of Working Group:

   The Network Modeling (NETMOD) working group is responsible for the YANG
   data modeling language, and guidelines for developing YANG models.  The
   NETMOD working group addresses general topics related to the use of the
   YANG language and YANG models, for example, the mapping of YANG modeled
   data into various encodings.  Finally, the NETMOD working group 
   also defines core YANG models used as basic YANG building blocks, and 
   YANG models that do not otherwise fall under the charter of any other 
   IETF working group.
  
The NETMOD WG is responsible for:

   a) Maintaining the data modeling language YANG.  This effort entails
      periodically updating the specification to address new requirements
      as they arise.

   b) Maintaining the guidelines for developing YANG models.  This effort
      is primarily driven by updates made to the YANG specification.

   c) Maintaining a conceptual framework in which YANG models are used.
      This effort entails describing the generic context that in YANG
      exists and how certain YANG statements interact in that context.
      An example of this is YANG's relationship with datastores.

   d) Maintaining encodings for YANG modeled data.  This effort entails
      updating encodings already defined by the NETMOD working (XML and
      JSON) to accommodate changes to the YANG specification, and defining
      new encodings that are needed, and yet do not fall under the charter
      of any other active IETF working group.

   e) Maintaining YANG models used as basic YANG building blocks.  This
      effort entails updating existing YANG models (ietf-yang-types and
      ietf-inet-types) as needed, as well as defining additional core YANG
      data models when necessary.

   f) Defining and maintaining YANG models that do not fall under the
      charter of any other active IETF working group.

   The NETMOD working group consults with the NETCONF working group to
   ensure that new requirements are and understood and can be met by
   the protocols developed within that working group (e.g., NETCONF
   and RESTCONF).  The NETMOD working group coordinates with other
   working groups on possible extensions to YANG to address new modeling
   requirements and, when needed, which group will run the process on a
   specific model.

   The NETMOD working group does not serve as a review team for YANG
   modules developed by other working groups. Instead, the YANG doctors,
   as organized by the OPS area director responsible for network
   management, will act as advisors for other working groups and provide
   YANG reviews for the OPS area directors.

Milestones:
  
   Done     - Submit draft-ietf-netmod-rfc6087bis to IESG for publication
   Mar 2017 - Submit draft-ietf-netmod-yang-model-classification to IESG
              for publication
   Mar 2017 - Submit draft-ietf-netmod-acl-model to IESG for publication
   Apr 2017 - Submit draft-ietf-netmod-entity to IESG for publication
   Apr 2017 - Submit draft-ietf-netmod-syslog-model to IESG for publication
   Oct 2017 - Submit draft-ietf-netmod-schema-mount to IESG for publication
   Oct 2017 - Submit draft-ietf-netmod-revised-datastores to IESG for
              publication
   Dec 2017 - Submit draft-ietf-netmod-intf-ext-yang to IESG for
              publication
   Dec 2017 - Submit draft-ietf-netmod-sub-intf-vlan-yang to IESG for
              publication