Re: [netmod] draft netmod charter update proposal

"Mehmet Ersue" <mersue@gmail.com> Tue, 07 March 2017 14:39 UTC

Return-Path: <mersue@gmail.com>
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 281381294FF; Tue, 7 Mar 2017 06:39:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M8etuNTGaMlf; Tue, 7 Mar 2017 06:38:48 -0800 (PST)
Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::229]) (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 440DB12952B; Tue, 7 Mar 2017 06:33:48 -0800 (PST)
Received: by mail-wr0-x229.google.com with SMTP id g10so2668959wrg.2; Tue, 07 Mar 2017 06:33:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=fvJrpgh8TPVxVwRCRaS8LTjVWQUxgvc7KY4wFZI9V+M=; b=ae5T2JENwyzO3UzneY3WsIi/d2U1WnZwabQIjVWjtUoXgSve55D/B4oQdyaY1ns1HN HJ4UYEal92EqYnxkMMO6qFN69IRhBFK59S+fpNYXUr38J5c+uu87/vyjBJt0Z0UdqXSt +HBxxdKFtbJs5M6bkzPg5ycLRsQy9PIbZfxk/1VBpu1A5j1ydNenx1GK1yS2lLY8OWJH cilFJ4v83wyo31K+UXpkqy4hLZeeEu36tZ7EYbt8gJv7/W2XQieSq49vvBX8GwegnIaA 6OHIfXT5ZVQwNBv9YoGuRjvYXP0vj+8aoTqdUghKHDrt6pVbJ4ikMsYoKBexjmvpvGba Ii7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=fvJrpgh8TPVxVwRCRaS8LTjVWQUxgvc7KY4wFZI9V+M=; b=j36Vc/Eb9cg+Ysjg8Vtm3tf5VZBWqe/JnsTahYJJzYioYbG0NBAzbGsskTgyff4QXu hMhaL3AeZgXpdAd+rrhSGqOQ8noL0MPjdfJDfODOBGDKms9QNaWHzTmeeEouDouEbH7O iYJz7zWV9ZfRpk19WS6afGUug2pVMMZKog0nah8RprBNb/Xq+eYPVNtE6UphResBDLqv 3CniqhAHUaHzIFRSWjzdMjR7OoY0O+Mdy2bL1h5bWVcwHfu/1qFfyXum60J4BRcK4pNa 2MyqeO1VhjqrjYYXisKV5Y8EbAcgE/0/34slGzmDbojv4CYokb/mKTKt+Q2XRqrF30yc YwNg==
X-Gm-Message-State: AMke39lJ3g2OzYJbVoixw5j8oAvdxfa0l1ibu0HL04PHYy7+c47O6Oujlj5DT9h964U6QA==
X-Received: by 10.223.139.196 with SMTP id w4mr570136wra.172.1488897226722; Tue, 07 Mar 2017 06:33:46 -0800 (PST)
Received: from DESKTOPFLHJVQJ (p5B341B45.dip0.t-ipconnect.de. [91.52.27.69]) by smtp.gmail.com with ESMTPSA id e16sm230482wra.36.2017.03.07.06.33.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Mar 2017 06:33:46 -0800 (PST)
From: Mehmet Ersue <mersue@gmail.com>
To: 'Kent Watsen' <kwatsen@juniper.net>, netmod@ietf.org
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> <030A7AF8-BA6E-4622-B008-F9624012C972@juniper.net>
In-Reply-To: <030A7AF8-BA6E-4622-B008-F9624012C972@juniper.net>
Date: Tue, 07 Mar 2017 15:33:47 +0100
Message-ID: <00f501d2974f$d4e08460$7ea18d20$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQH7oic/U5hpx/GFJ0RcyrWSlwEP7gFUc6bxAwunfXMCshfA6wGwTOtXApSHeBag26D4AA==
Content-Language: de
X-AVK-Virus-Check: AVA 25.10928;F984776D
X-AVK-Spam-Check: 1; str=0001.0A0C0205.58BEC4C9.02BC,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0; AE713
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/7KRMHDpjM-m3svTubAs8kpD2Dj0>
Cc: 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: Tue, 07 Mar 2017 14:39:06 -0000

Hi Kent,

I am missing two aspects in the charter.
One is the short description of planned WG items setting the target. 
The other point is the intended status of the WG items.
To me without such definition it looks kind of incomplete.

Mehmet

> -----Original Message-----
> From: netmod [mailto:netmod-bounces@ietf.org] On Behalf Of Kent Watsen
> Sent: Friday, March 3, 2017 4:23 PM
> To: netmod@ietf.org
> Cc: netmod-chairs@ietf.org
> Subject: Re: [netmod] draft netmod charter update proposal
> 
> 
> 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
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod